CVE-2026-72447: sctp: hold socket lock when dumping endpoints in sctp_diag
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 207bb4ce8fe7de961ae7bb33569ad2cd61f44954, 722576aba0a6d9423714550b1c03239b0f0def77, 7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823.
Low priority for now. Upgrade to Linux Linux 207bb4ce8fe7de961ae7bb33569ad2cd61f44954, 722576aba0a6d9423714550b1c03239b0f0def77, 7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.7affected
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before f98c294a9369b6fe89e652c06357ee594be4dfa2affected · git
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before 8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8aaffected · git
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before ec3c2d59a192e17e1014ba71afc368ba162ecac3affected · git
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before 722576aba0a6d9423714550b1c03239b0f0def77affected · git
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before abe7f8828e6ac8be858870c2bf836258844f97d5affected · git
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before 207bb4ce8fe7de961ae7bb33569ad2cd61f44954affected · git
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before f09a245f33e567b604efa1960b7a2d25dd9c8713affected · git
- 8f840e47f190cbe61a96945c13e9551048d42cef and later · before 7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823affected · git
- before 4.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72441Aug 15, 2026 · ieee802154: fix kernel-infoleak in dgram_recvmsg()0Monitor
- ← EarlierCVE-2026-72444Aug 15, 2026 · flow_dissector: check device type before reading ETH_ADDRS31Monitor
- Later →CVE-2026-72449Aug 15, 2026 · drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 207bb4ce8fe7de961ae7bb33569ad2cd61f44954 | Vendor (CNA) |
| Linux Linux | 722576aba0a6d9423714550b1c03239b0f0def77 | Vendor (CNA) |
| Linux Linux | 7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823 | Vendor (CNA) |
| Linux Linux | 8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8a | Vendor (CNA) |
| Linux Linux | abe7f8828e6ac8be858870c2bf836258844f97d5 | Vendor (CNA) |
| Linux Linux | ec3c2d59a192e17e1014ba71afc368ba162ecac3 | Vendor (CNA) |
| Linux Linux | f09a245f33e567b604efa1960b7a2d25dd9c8713 | Vendor (CNA) |
| Linux Linux | f98c294a9369b6fe89e652c06357ee594be4dfa2 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/722576aba0a6d9423714550b1c03239b0f0def77
- git.kernel.org/stable/c/7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823
- git.kernel.org/stable/c/8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8a
- git.kernel.org/stable/c/abe7f8828e6ac8be858870c2bf836258844f97d5
- git.kernel.org/stable/c/ec3c2d59a192e17e1014ba71afc368ba162ecac3
- git.kernel.org/stable/c/f09a245f33e567b604efa1960b7a2d25dd9c8713
- git.kernel.org/stable/c/f98c294a9369b6fe89e652c06357ee594be4dfa2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.