Description
In the Linux kernel, the following vulnerability has been resolved: sctp: fix addr_wq_timer race in sctp_free_addr_wq() sctp_free_addr_wq() previously removed addr_wq_timer using timer_delete() while holding addr_wq_lock. However, timer_delete() does not guarantee that a currently running timer handler has completed. This allows a race with sctp_addr_wq_timeout_handler(), where the handler may still run after addr_waitq has been freed, acquire addr_wq_lock, and access freed memory, leading to a use-after-free. Fix this by calling timer_shutdown_sync() before taking addr_wq_lock. This guarantees that any in-flight timer handler has finished and prevents the timer from being re-armed during teardown, making subsequent cleanup safe.
References6
- git.kernel.org/stable/c/5098308ad72f83f3b1a48c247dddab1695114bae
- git.kernel.org/stable/c/976c19de0f22a857ba0112f39635f8fd7a257568
- git.kernel.org/stable/c/a8323fb2ab6cd6978f359daeed6688e0cadf32ba
- git.kernel.org/stable/c/c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1
- git.kernel.org/stable/c/d49eff15261dd62e4fa3a316c26cb1f537a60464
- git.kernel.org/stable/c/fb6117713abef8646fdbf58256532451bcf26c47
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 6 · as of 11 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.