sctp: stream: fully roll back denied add-stream state
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 637784ade221a3c8a7ecd0f583eddd95d6276b9a · < d5ea0b3e261fcb2cfff142675516165244cab1da| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
When an SCTP ADD_OUT_STREAMS request is denied, the Linux kernel can leave stale outgoing-stream metadata behind. A later re-add can reuse that metadata and trigger a null-pointer dereference in the scheduler. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Engineers running the Linux kernel should check whether their kernel includes the SCTP stream rollback fix; affected versions are not specified.