CVE-2026-72447: Linux kernel · sctp: hold socket lock when dumping endpoints in sctp_diag
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f98c294a9369b6fe89e652c06357ee594be4dfa2 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 18:11 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in f98c294a9369b6fe89e652c06357ee594be4dfa2, f09a245f33e567b604efa1960b7a2d25dd9c8713, ec3c2d59a192e17e1014ba71afc368ba162ecac3 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in multiple Linux kernel commits. Users and administrators should update to a Linux kernel version that includes these fixes. Since this is a kernel-level vulnerability, applying the official kernel patches or upgrading to a fixed kernel release is the recommended remediation. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel SCTP implementation allowed concurrent access to endpoint address lists without proper locking, leading to a potential information leak of uninitialized memory to userspace. This was due to the SCTP_DIAG endpoint dumping traversing address lists without holding the socket lock, causing a race condition. The issue has been fixed by introducing proper locking and traversal mechanisms.
References
- git.kernel.org/stable/c/f98c294a9369b6fe89e652c06357ee594be4dfa2 (opens in a new tab)
- git.kernel.org/stable/c/8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8a (opens in a new tab)
- git.kernel.org/stable/c/ec3c2d59a192e17e1014ba71afc368ba162ecac3 (opens in a new tab)
- git.kernel.org/stable/c/722576aba0a6d9423714550b1c03239b0f0def77 (opens in a new tab)
- git.kernel.org/stable/c/abe7f8828e6ac8be858870c2bf836258844f97d5 (opens in a new tab)
- git.kernel.org/stable/c/207bb4ce8fe7de961ae7bb33569ad2cd61f44954 (opens in a new tab)
- git.kernel.org/stable/c/f09a245f33e567b604efa1960b7a2d25dd9c8713 (opens in a new tab)
- git.kernel.org/stable/c/7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823 (opens in a new tab)