CVE-2026-23302: net: annotate data-races around sk->sk_{data_ready,write_space}
In the Linux kernel, the following vulnerability has been resolved:
net: annotate data-races around sk->sk_{data_ready,write_space}
skmsg (and probably other layers) are changing these pointers
while other cpus might read them concurrently.
Add corresponding READ_ONCE()/WRITE_ONCE() annotations
for UDP, TCP and AF_UNIX.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23302 is a Linux kernel networking fix for unsafe concurrent access to socket callback pointers. The public record does not state business impact, severity, CVSS, or active exploitation. Treat it as a kernel maintenance and exposure-tracking issue until Linux distribution advisories clarify risk.
Executive priority
Monitor and patch through normal kernel update channels unless your vendor assigns higher severity. There is not enough public evidence here to justify emergency response, but kernel data-race fixes should not be ignored on internet-facing or multi-tenant infrastructure.
Technical view
The fix annotates data races around sk->sk_data_ready and sk->sk_write_space using READ_ONCE()/WRITE_ONCE() in UDP, TCP, and AF_UNIX paths. skmsg and possibly other layers can change these pointers while other CPUs read them concurrently. No CWE, CVSS, or exploit prerequisites are provided.
Likely exposure
Exposure applies to Linux systems running affected kernel lines identified in the CVE record. The source data lists Linux as affected across version entries including 4.20, 6.1.177, 6.6.136, 6.12.82, 6.18.17, 6.19.7, and 7.0, but distribution package mapping is not provided.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation, proof-of-concept availability, attacker requirements, or reliable impact. The issue is described as a kernel data-race correction, not as a demonstrated privilege escalation or remote attack path.
Researcher notes
Focus validation on kernel provenance and whether the READ_ONCE()/WRITE_ONCE() changes for socket callbacks are present. The record does not establish exploitability, affected configurations beyond Linux kernel versions, or downstream distribution status, so avoid drawing conclusions beyond the cited commits.
Mitigation direction
Check Linux vendor or distribution advisories for fixed kernel packages.
Prioritize kernel updates where affected versions are present.
Track the referenced stable kernel commits in patch management records.
Avoid inventing compensating controls until vendor guidance defines impact.
Validation and detection
Inventory running kernel versions across servers, endpoints, appliances, and containers hosts.
Compare deployed kernels with vendor advisories for CVE-2026-23302.
Confirm whether referenced stable commits are included in your kernel build.
Document systems awaiting vendor-fixed packages or maintenance windows.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23302 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 25, 2026, 10:26 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.