Answer in brief
CVE-2026-72383 records a High severity (CVSS 7.8) vulnerability in sctp: fix addr_wq_timer race in sctp_free_addr_wq(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4db67e808640e3934d82ce61ee8e2e89fd877ba8 <a8323fb2ab6cd6978f359daeed6688e0cadf32ba || >=4db67e808640e3934d82ce61ee8e2e89fd877ba8 <c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1 || >=4db67e808640e3934d82ce61ee8e2e89fd877ba8 <976c19de0f22a857ba0112f39635f8fd7a257568 | a8323fb2ab6cd6978f359daeed6688e0cadf32ba, c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1, 976c19de0f22a857ba0112f39635f8fd7a257568 |
| Linux/Linuxgeneric | 3.7 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.