CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak
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.13% (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 2a9ea988465ece5b6896b1bdc144170a64e84c35, 5172adf9efb8298a52f4dcdc3f98d4d9d1e06a6d, 60abb0ac11dccd6b98fd9182bc5f85b621688861.
Low priority for now. Upgrade to Linux Linux 2a9ea988465ece5b6896b1bdc144170a64e84c35, 5172adf9efb8298a52f4dcdc3f98d4d9d1e06a6d, 60abb0ac11dccd6b98fd9182bc5f85b621688861 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: Fix fragment node deletion to prevent buffer leak After commit b692bf9a7543 ("xsk: Get rid of xdp_buff_xsk::xskb_list_node"), the list_node field is reused for both the xskb pool list and the buffer free list, this causes a buffer leak as described below. xp_free() checks if a buffer is already on the free list using list_empty(&xskb->list_node). When list_del() is used to remove a node from the xskb pool list, it doesn't reinitialize the node pointers. This means list_empty() will return false even after the node has been removed, causing xp_free() to incorrectly skip adding the buffer to the free list. Fix this by using list_del_init() instead of list_del() in all fragment handling paths, this ensures the list node is reinitialized after removal, allowing the list_empty() to work correctly.
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-787
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%
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.13.1 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel6.13
- 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
- 6.13affected
- 560c974b7ccd95bb9ff20df77f6654283e45c9c6 and later · before 5172adf9efb8298a52f4dcdc3f98d4d9d1e06a6daffected · git
- fd5614763805d6f386bd07cc53558f88b1b1eb62 and later · before 2a9ea988465ece5b6896b1bdc144170a64e84c35affected · git
- b692bf9a7543af7ad11a59d182a3757578f0ba53 and later · before 645c6d8376ad4913cbffe0e0c2cca0c4febbe596affected · git
- b692bf9a7543af7ad11a59d182a3757578f0ba53 and later · before b38cbd4af5034635cff109e08788c63f956f3a69affected · git
- b692bf9a7543af7ad11a59d182a3757578f0ba53 and later · before 60abb0ac11dccd6b98fd9182bc5f85b621688861affected · git
- before 6.13not affected · semver
- 6.18.17 and later · up to and including 6.18.*not affected · semver
- 6.19.7 and later · up to and including 6.19.*not affected · semver
- 7.0 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: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-23324Mar 25, 2026 · can: usb: etas_es58x: correctly anchor the urb in the read bulk callback22Monitor
- ← EarlierCVE-2026-23325Mar 25, 2026 · wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211()28Monitor
- Later →CVE-2026-23329Mar 25, 2026 · libie: don't unroll if fwlog isn't supported22Monitor
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 | 2a9ea988465ece5b6896b1bdc144170a64e84c35 | Vendor (CNA) |
| Linux Linux | 5172adf9efb8298a52f4dcdc3f98d4d9d1e06a6d | Vendor (CNA) |
| Linux Linux | 60abb0ac11dccd6b98fd9182bc5f85b621688861 | Vendor (CNA) |
| Linux Linux | 645c6d8376ad4913cbffe0e0c2cca0c4febbe596 | Vendor (CNA) |
| Linux Linux | b38cbd4af5034635cff109e08788c63f956f3a69 | Vendor (CNA) |
| debian:linux | 6.19.8-1 · Debian:14 | 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.
- 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-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.