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-72447sctp: hold socket lock when dumping endpoints in sctp_diag

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: hold socket lock when dumping endpoints in sctp_diag SCTP_DIAG endpoint dumping was traversing endpoint address lists without holding lock_sock(), while those lists could change concurrently via socket operations (e.g., bindx changes). This creates a race where nla_reserve() counts addresses under RCU protection, but the subsequent copy may see fewer entries, potentially leaking uninitialized memory to userspace. Fix this by: - Taking a reference on each endpoint during hash traversal - Moving socket operations (lock_sock()) outside read_lock_bh() - Serializing address list access during dump - Reworking sctp_for_each_endpoint() to support restart-based traversal with (net, pos) tracking Also: - Add WARN_ON_ONCE() for inconsistent address counts - Fix idiag_states filtering for LISTEN vs association cases - Skip dumping endpoints being freed (ep->base.dead) - Move dump position tracking into iterator, removing cb->args[4] and its comment for sctp_ep_dump()., - Update the comment for cb->args[4] and remove the comment for unused cb->args[5] for sctp_sock_dump(). Note: traversal is restart-based and may re-scan buckets multiple times, but this is acceptable due to small bucket sizes and required to support sleeping-safe callbacks. This issue was reported by Nico Yip (@_cyeaa_) working with TrendAI Zero Day Initiative.

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < f98c294a9369b6fe89e652c06357ee594be4dfa2
    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < 8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8a
    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < ec3c2d59a192e17e1014ba71afc368ba162ecac3
    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < 722576aba0a6d9423714550b1c03239b0f0def77
    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < abe7f8828e6ac8be858870c2bf836258844f97d5
    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < 207bb4ce8fe7de961ae7bb33569ad2cd61f44954
    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < f09a245f33e567b604efa1960b7a2d25dd9c8713
    • affected 8f840e47f190cbe61a96945c13e9551048d42cef – < 7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .