CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq()
In the Linux kernel, the following vulnerability has been resolved:
sctp: fix addrwqtimer race in sctpfreeaddrwq()
sctpfreeaddrwq() previously removed addrwqtimer using timerdelete() while holding addrwqlock. However, timerdelete() does not guarantee that a currently running timer handler has completed.
This allows a race with sctpaddrwqtimeouthandler(), where the handler may still run after addrwaitq has been freed, acquire addrwqlock, and access freed memory, leading to a use-after-free.
Fix this by calling timershutdownsync() before taking addrwqlock. This guarantees that any in-flight timer handler has finished and prevents the timer from being re-armed during teardown, making subsequent cleanup safe.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72383?
CVE-2026-72383 has a risk score of 47, indicating a moderate severity level.
What kind of vulnerability is CVE-2026-72383?
CVE-2026-72383 is classified as a Use After Free vulnerability in the Linux kernel.
How do I fix CVE-2026-72383?
To fix CVE-2026-72383, update the Linux kernel to the latest version where this vulnerability has been resolved.
What component of the Linux kernel is affected by CVE-2026-72383?
CVE-2026-72383 affects the sctp (Stream Control Transmission Protocol) component of the Linux kernel.
What is the impact of CVE-2026-72383?
The impact of CVE-2026-72383 includes potential instability or security issues due to race conditions in timer handling.