CVE-2026-53250: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()
Noroxi assessment
Priority: Monitor (action score 31/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.10% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0dfe05b938435892875e07771170051346412df9, 22ba97ea9cc1f63a0d0244fae38057ed452b6ac7, bfdfd2706d5fb2cd496a1506e680daf979309c8b.
Low priority for now. Upgrade to Linux Linux 0dfe05b938435892875e07771170051346412df9, 22ba97ea9cc1f63a0d0244fae38057ed452b6ac7, bfdfd2706d5fb2cd496a1506e680daf979309c8b 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: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path. Fix this by reading csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment. Note that other metadata fields (flags, launch_time) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.
- Published
- Jun 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-367
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 kernel6.8 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- linux linux kernel7.1
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
- 6.8affected
- 48eb03dd26304c24f03bdbb9382e89c8564e71df and later · before eb778aed8a9b2381668fcb1247ae4fa011224768affected · git
- 48eb03dd26304c24f03bdbb9382e89c8564e71df and later · before 0dfe05b938435892875e07771170051346412df9affected · git
- 48eb03dd26304c24f03bdbb9382e89c8564e71df and later · before bfdfd2706d5fb2cd496a1506e680daf979309c8baffected · git
- 48eb03dd26304c24f03bdbb9382e89c8564e71df and later · before 22ba97ea9cc1f63a0d0244fae38057ed452b6ac7affected · git
- before 6.8not affected · semver
- 6.12.110 and later · up to and including 6.12.*not affected · semver
- 6.18.36 and later · up to and including 6.18.*not affected · semver
- 7.0.13 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
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-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.0.13-1 | 7.0.13-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-53246Jun 25, 2026 · sctp: validate cached peer INIT chunk length in COOKIE_ECHO processing39Monitor
- ← EarlierCVE-2026-53249Jun 25, 2026 · ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options22Monitor
- Later →CVE-2026-53251Jun 25, 2026 · Bluetooth: ISO: Fix not releasing hdev reference on iso_conn_big_sync22Monitor
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 | 0dfe05b938435892875e07771170051346412df9 | Vendor (CNA) |
| Linux Linux | 22ba97ea9cc1f63a0d0244fae38057ed452b6ac7 | Vendor (CNA) |
| Linux Linux | bfdfd2706d5fb2cd496a1506e680daf979309c8b | Vendor (CNA) |
| Linux Linux | eb778aed8a9b2381668fcb1247ae4fa011224768 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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.
- CVE-2025-38352338 days apartposix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()KEV61This week
- CVE-2026-6409124 days apartbatman-adv: tt: fix TOCTOU race for reported vlans39Monitor
- CVE-2026-6403424 days apartnet: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer37Monitor
- CVE-2026-6393724 days apartKVM: SEV: Use READ_ONCE() when reading entries/indices from PSC buffer35Monitor
- CVE-2026-6386724 days apartmptcp: close TOCTOU race while computing rcv_wnd32Monitor
- CVE-2026-531450 days apartdrm/gem: Try to fix change_handle ioctl, attempt 431Monitor
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.