sctp: fix addr_wq_timer race in sctp_free_addr_wq()
CVE-2026-72383 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-72383?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 4db67e808640e3934d82ce61ee8e2e89fd877ba8 to < 5098308ad72f83f3b1a48c247dddab1695114bae, 4db67e808640e3934d82ce61ee8e2e89fd877ba8 to < d49eff15261dd62e4fa3a316c26cb1f537a60464, 4db67e808640e3934d82ce61ee8e2e89fd877ba8 to < a8323fb2ab6cd6978f359daeed6688e0cadf32ba, 4db67e808640e3934d82ce61ee8e2e89fd877ba8 to < c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1
- Linux Linux: 3.7
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/5098308ad72f83f3b1a48c247dddab1695114bae
- git.kernel.org/stable/c/d49eff15261dd62e4fa3a316c26cb1f537a60464
- git.kernel.org/stable/c/a8323fb2ab6cd6978f359daeed6688e0cadf32ba
- git.kernel.org/stable/c/c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1
- git.kernel.org/stable/c/976c19de0f22a857ba0112f39635f8fd7a257568
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON