CVE-2026-23302: net: annotate data-races around sk->sk_{data_ready,write_space}
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 279f2b67d1c44ee139bd3fdb221850daa9358449, 27fccdbcbbfc4651b6f66756e6fa3f52e051ec23, 2ef2b20cf4e04ac8a6ba68493f8780776ff84300; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1.
Low priority for now. Upgrade to Linux Linux 279f2b67d1c44ee139bd3fdb221850daa9358449, 27fccdbcbbfc4651b6f66756e6fa3f52e051ec23, 2ef2b20cf4e04ac8a6ba68493f8780776ff84300; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 25, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-362
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.20 and later · before 6.6.136
- linux linux kernel6.7 and later · before 6.12.82
- linux linux kernel6.13 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.20affected
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 279f2b67d1c44ee139bd3fdb221850daa9358449affected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 7ad01905831c815520f1b0486336a03bb7420465affected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before c494448bb522bbbb63096540eb2319101a0480abaffected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before f17c1c4acbe2bd702abce73a847a04a196fab2c5affected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 27fccdbcbbfc4651b6f66756e6fa3f52e051ec23affected · git
- 604326b41a6fb9b4a78b6179335decee0365cd8c and later · before 2ef2b20cf4e04ac8a6ba68493f8780776ff84300affected · git
- before 4.20not affected · semver
- 6.1.177 and later · up to and including 6.1.*not affected · semver
- 6.6.136 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.177-1 | 6.1.177-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.8-1 | 6.19.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23296Mar 25, 2026 · scsi: core: Fix refcount leak for tagset_refcnt22Monitor
- ← EarlierCVE-2026-23300Mar 25, 2026 · net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop22Monitor
- Later →CVE-2026-23303Mar 25, 2026 · smb: client: Don't log plaintext credentials in cifs_set_cifscreds22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 279f2b67d1c44ee139bd3fdb221850daa9358449 | Vendor (CNA) |
| Linux Linux | 27fccdbcbbfc4651b6f66756e6fa3f52e051ec23 | Vendor (CNA) |
| Linux Linux | 2ef2b20cf4e04ac8a6ba68493f8780776ff84300 | Vendor (CNA) |
| Linux Linux | 7ad01905831c815520f1b0486336a03bb7420465 | Vendor (CNA) |
| Linux Linux | c494448bb522bbbb63096540eb2319101a0480ab | Vendor (CNA) |
| Linux Linux | f17c1c4acbe2bd702abce73a847a04a196fab2c5 | Vendor (CNA) |
| azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 | 6.6.137.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.177-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/27fccdbcbbfc4651b6f66756e6fa3f52e051ec23
- git.kernel.org/stable/c/2ef2b20cf4e04ac8a6ba68493f8780776ff84300
- git.kernel.org/stable/c/7ad01905831c815520f1b0486336a03bb7420465
- git.kernel.org/stable/c/c494448bb522bbbb63096540eb2319101a0480ab
- git.kernel.org/stable/c/f17c1c4acbe2bd702abce73a847a04a196fab2c5
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.