Skip to main content
VulnerabilityPublished Updated

CVE-2026-23302: Linux kernel · net: annotate data-races around sk->sk_{data_ready,write_space}

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f17c1c4acbe2bd702abce73a847a04a196fab2c5 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:24 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
EPSS
0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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-05.

Patch
Available – fixed in f17c1c4acbe2bd702abce73a847a04a196fab2c5, c494448bb522bbbb63096540eb2319101a0480ab, 279f2b67d1c44ee139bd3fdb221850daa9358449 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 604326b41a6fb9b4a78b6179335decee0365cd8c, < f17c1c4acbe2bd702abce73a847a04a196fab2c5
Fixed in
  • f17c1c4acbe2bd702abce73a847a04a196fab2c5
LinuxLinuxAffected
  • ≥ 604326b41a6fb9b4a78b6179335decee0365cd8c, < c494448bb522bbbb63096540eb2319101a0480ab
Fixed in
  • c494448bb522bbbb63096540eb2319101a0480ab
LinuxLinuxAffected
  • ≥ 604326b41a6fb9b4a78b6179335decee0365cd8c, < 279f2b67d1c44ee139bd3fdb221850daa9358449
Fixed in
  • 279f2b67d1c44ee139bd3fdb221850daa9358449
LinuxLinuxAffected
  • ≥ 604326b41a6fb9b4a78b6179335decee0365cd8c, < 27fccdbcbbfc4651b6f66756e6fa3f52e051ec23
Fixed in
  • 27fccdbcbbfc4651b6f66756e6fa3f52e051ec23
LinuxLinuxAffected
  • ≥ 604326b41a6fb9b4a78b6179335decee0365cd8c, < 7ad01905831c815520f1b0486336a03bb7420465
Fixed in
  • 7ad01905831c815520f1b0486336a03bb7420465
LinuxLinuxAffected
  • ≥ 604326b41a6fb9b4a78b6179335decee0365cd8c, < 2ef2b20cf4e04ac8a6ba68493f8780776ff84300
Fixed in
  • 2ef2b20cf4e04ac8a6ba68493f8780776ff84300

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.

References

Community reviews

Loading reviews…