Bug 2492108 (CVE-2026-52929) - CVE-2026-52929 kernel: sctp: stream: fully roll back denied add-stream state
Summary: CVE-2026-52929 kernel: sctp: stream: fully roll back denied add-stream state
Keywords:
Status: NEW
Alias: CVE-2026-52929
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-24 08:02 UTC by OSIDB Bzimport
Modified: 2026-08-21 04:05 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-24 08:02:20 UTC
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.

Comment 3 Akiyoshi Kurita 2026-08-21 04:05:06 UTC
FYI:

A public exploit for CVE-2026-52929 has been released.

Public exploit:
https://github.com/NebuSec/CyberMeowfia/tree/main/security-research/Linux-CVE-2026-52929-Ubuntu-7.0.0-28

Demo video:
https://x.com/nebusecurity/status/2090585257540259971

Relevant stable kernel fixes / reference patches:

RHEL 8 reference (5.10 stable backport):
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0cd2dc6dce8ca47212cd306ccd52eb315ef3cf85

RHEL 9 reference (5.15 stable backport):
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a6724b7b812ac8793514a1d5938db5d9d29ae725

RHEL 10 reference (6.12 stable):
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=39dc2b0eb5371a669ebc9ec6072b9184eac95418

For RHEL 8, the 5.10 stable commit is provided as a reference because there is no corresponding maintained upstream 4.18 stable branch. A RHEL 8 fix may therefore require a separate backport.

Possible mitigation if SCTP is not required:

echo "install sctp /bin/false" > /etc/modprobe.d/disable-sctp.conf

This prevents the sctp kernel module from being loaded and can reduce exposure on systems that do not require SCTP.


Note You need to log in before you can comment on or make changes to this bug.