Skip to main content
VulnerabilityPublished Updated

CVE-2026-52929: Linux kernel · sctp: stream: fully roll back denied add-stream state

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in d5ea0b3e261fcb2cfff142675516165244cab1da : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in d5ea0b3e261fcb2cfff142675516165244cab1da, a6724b7b812ac8793514a1d5938db5d9d29ae725, a5f8a90ac9f77c678a9781c0a464b635e0d63e49 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 637784ade221a3c8a7ecd0f583eddd95d6276b9a, < d5ea0b3e261fcb2cfff142675516165244cab1da
Fixed in
  • d5ea0b3e261fcb2cfff142675516165244cab1da
LinuxLinuxAffected
  • ≥ 637784ade221a3c8a7ecd0f583eddd95d6276b9a, < a6724b7b812ac8793514a1d5938db5d9d29ae725
Fixed in
  • a6724b7b812ac8793514a1d5938db5d9d29ae725
LinuxLinuxAffected
  • ≥ 637784ade221a3c8a7ecd0f583eddd95d6276b9a, < a5f8a90ac9f77c678a9781c0a464b635e0d63e49
Fixed in
  • a5f8a90ac9f77c678a9781c0a464b635e0d63e49
LinuxLinuxAffected
  • ≥ 637784ade221a3c8a7ecd0f583eddd95d6276b9a, < 9662eb0401518f0b4681f10e7fbf688f504f24cf
Fixed in
  • 9662eb0401518f0b4681f10e7fbf688f504f24cf
LinuxLinuxAffected
  • ≥ 637784ade221a3c8a7ecd0f583eddd95d6276b9a, < 39dc2b0eb5371a669ebc9ec6072b9184eac95418
Fixed in
  • 39dc2b0eb5371a669ebc9ec6072b9184eac95418
LinuxLinuxAffected
  • ≥ 637784ade221a3c8a7ecd0f583eddd95d6276b9a, < 7dd9a42b044aad2dbe037db1c1e2943582485b44
Fixed in
  • 7dd9a42b044aad2dbe037db1c1e2943582485b44

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: stream: fully roll back denied add-stream state When ADD_OUT_STREAMS is denied, SCTP only shrinks the queued chunks and then lowers outcnt. That leaves removed stream metadata behind, so a later re-add can reuse a stale ext and hit a null-pointer dereference in the scheduler get path. Fix the rollback by tearing down the removed stream state the same way other stream resizes do. Unschedule the current scheduler state, drop the removed stream ext state with sctp_stream_outq_migrate(), and then reschedule the remaining streams. This keeps scheduler-private RR/FC/PRIO lists consistent while fully rolling back denied outgoing stream additions.

References

Community reviews

Loading reviews…