sctp: fix addr_wq_timer race in sctp_free_addr_wq()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4db67e808640e3934d82ce61ee8e2e89fd877ba8 · < 976c19de0f22a857ba0112f39635f8fd7a257568| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel SCTP address work queue has a timer race during cleanup. If the timer handler is still running after the queue is freed, it can access freed memory; the input does not establish how an attacker could trigger the race or whether access or user interaction is required.
Engineers running Linux kernels with SCTP should check whether their kernel includes the fix; affected versions were not provided.