Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72383sctp: fix addr_wq_timer race in sctp_free_addr_wq()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-72383, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 4db67e808640e3934d82ce61ee8e2e89fd877ba8 – < fb6117713abef8646fdbf58256532451bcf26c47
    • affected 4db67e808640e3934d82ce61ee8e2e89fd877ba8 – < 5098308ad72f83f3b1a48c247dddab1695114bae
    • affected 4db67e808640e3934d82ce61ee8e2e89fd877ba8 – < d49eff15261dd62e4fa3a316c26cb1f537a60464
    • affected 4db67e808640e3934d82ce61ee8e2e89fd877ba8 – < a8323fb2ab6cd6978f359daeed6688e0cadf32ba
    • affected 4db67e808640e3934d82ce61ee8e2e89fd877ba8 – < c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1
    • affected 4db67e808640e3934d82ce61ee8e2e89fd877ba8 – < 976c19de0f22a857ba0112f39635f8fd7a257568
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72383 badge
[![CVE-2026-72383](https://cveledger.app/badge/CVE-2026-72383.svg)](https://cveledger.app/cve/CVE-2026-72383)

Record last updated .