sctp: fix use-after-free of cached ASCONF chunk
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: sctp: fix use-after-free of cached ASCONF chunk addip_last_asconf caches the outstanding outbound ASCONF chunk. The normal ASCONF-ACK completion path releases the chunk and clears the pointer. However, sctp_asconf_queue_teardown() releases the cached chunk without clearing addip_last_asconf. During peer restart handling, sctp_sf_do_dupcook_a() queues SCTP_CMD_PURGE_ASCONF_QUEUE, which invokes sctp_asconf_queue_teardown() while the association remains alive and leaves the pointer dangling. A delayed authenticated ASCONF-ACK can then reach sctp_sf_do_asconf_ack(), which accesses the stale chunk and passes it to sctp_process_asconf_ack(), causing a use-after-free and a second release. Clearing the pointer exposes a race with T4 expiry. Peer restart handling queues the timer stop before the purge, but SCTP_CMD_TIMER_STOP uses timer_delete(), which does not wait for a callback already running on another CPU. Such a callback can reach sctp_sf_t4_timer_expire() after the purge and dereference NULL. Clear addip_last_asconf after releasing the cached chunk, and make sctp_sf_t4_timer_expire() consume a stale T4 expiry if no outstanding ASCONF remains.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in 10459b03e2d9ee12435e96f587de4d4cacdbf435; From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in e1bb114e09372fd6e03387ced9ef566da336ed6c; From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in 179676f0166230c80053a392303485b37c93dd33; From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in dc67d528c2fa939cec7fe3bf7f3089c8d281ca3d; From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in 618b5c6d049896fcfabb91afc072954c92cb2693; From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in 07daf4f9750104960a1d60831b2353c0d41f35fb; From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in d949992bc3f00027a2c755e860a11950c75f6073; From a000c01e60e40e15304ffe48fff051d17a7bea91 · fixed in 8c283e7b56adce00193837f3311b06662466fb21
- Linux Linux
3.0
- KernelLinux
From 3.0.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.152; From 6.7.0 · fixed in 6.12.104; From 6.13.0 · fixed in 6.18.45; From 6.19.0 · fixed in 7.1.9
References 8
git.kernel.org
- stable/c/10459b03e2d9ee12435e96f587de4d4cacdbf435
- stable/c/e1bb114e09372fd6e03387ced9ef566da336ed6c
- stable/c/179676f0166230c80053a392303485b37c93dd33
- stable/c/dc67d528c2fa939cec7fe3bf7f3089c8d281ca3d
- stable/c/618b5c6d049896fcfabb91afc072954c92cb2693
- stable/c/07daf4f9750104960a1d60831b2353c0d41f35fb
- stable/c/d949992bc3f00027a2c755e860a11950c75f6073
- stable/c/8c283e7b56adce00193837f3311b06662466fb21