CVE-2026-72447
Last modified
CVE-2026-72447 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 8f840e47f190cbe61a96945c13e9551048d42cef, < f98c294a9369b6fe89e652c06357ee594be4dfa2; >= 8f840e47f190cbe61a96945c13e9551048d42cef, < 8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8a; >= 8f840e47f190cbe61a96945c13e9551048d42cef, < ec3c2d59a192e17e1014ba71afc368ba162ecac3; >= 8f840e47f190cbe61a96945c13e9551048d42cef, < 722576aba0a6d9423714550b1c03239b0f0def77; >= 8f840e47f190cbe61a96945c13e9551048d42cef, < abe7f8828e6ac8be858870c2bf836258844f97d5; >= 8f840e47f190cbe61a96945c13e9551048d42cef, < 207bb4ce8fe7de961ae7bb33569ad2cd61f44954; >= 8f840e47f190cbe61a96945c13e9551048d42cef, < f09a245f33e567b604efa1960b7a2d25dd9c8713; >= 8f840e47f190cbe61a96945c13e9551048d42cef, < 7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823 |
| Linux | Linux | 4.7 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72447?
How severe is CVE-2026-72447?
How do I fix CVE-2026-72447?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72441In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72442In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72443In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72444In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72445In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72446In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72448In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72449In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72450In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72451In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72452In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72453In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-72447?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
