CVE-2026-23302
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
The Linux kernel lacks READ_ONCE()/WRITE_ONCE() annotations for sk->sk_data_ready and sk->sk_write_space, leading to data races that can cause malfunctions in UDP, TCP, and AF_UNIX sockets under concurrent access.
Vulnerability
Description
CVE-2026-23302 addresses a concurrency issue in the Linux kernel's networking subsystem. The sk_data_ready and sk_write_space pointers in the socket structure (struct sock) are modified by skmsg and other layers, yet they are read concurrently by other CPUs. Without proper READ_ONCE() and WRITE_ONCE() annotations, these accesses constitute data races per the C memory model, which can lead to torn reads or compiler-optimized re-reads, resulting in stale or inconsistent pointer values.
Exploitation
Scenario
An attacker with the ability to trigger concurrent socket operations (e.g., via crafted network traffic or local exploitation of BPF/skmsg) could potentially exploit these races. When a reader CPU sees an intermediate or stale value of sk_data_ready or sk_write_space, the kernel might invoke the wrong callback, skip notification, or double-invoke it. This exploitable window exists across UDP, TCP, and AF_UNIX sockets, as all three modify and inspect these pointers without atomicity guarantees.
Impact
Successful exploitation could cause denial of service (e.g., a socket failing to wake up when data arrives, or waking up spuriously), memory corruption if callbacks are misdirected, or information disclosure if notification is improperly delayed. In theory, an attacker controlling the value of a callback pointer could redirect execution, though practical exploitation would require additional primitive chaining.
Mitigation
Status
The fix was committed to the Linux kernel stable repository; the referenced commits [1][2][3][4] add the required READ_ONCE()/WRITE_ONCE() annotations. Users should update to a kernel version containing these commits. No workaround is available beyond patching, as this is a semantic correctness fix. The vulnerability is not yet listed on CISA's Known Exploited Vulnerabilities (KEV) catalog.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- git.kernel.org/stable/c/27fccdbcbbfc4651b6f66756e6fa3f52e051ec23nvd
- git.kernel.org/stable/c/2ef2b20cf4e04ac8a6ba68493f8780776ff84300nvd
- git.kernel.org/stable/c/7ad01905831c815520f1b0486336a03bb7420465nvd
- git.kernel.org/stable/c/c494448bb522bbbb63096540eb2319101a0480abnvd
- git.kernel.org/stable/c/f17c1c4acbe2bd702abce73a847a04a196fab2c5nvd
News mentions
0No linked articles in our index yet.