CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23326 is a Linux kernel defect in xsk/AF_XDP buffer handling. A coding error can leak buffers instead of returning them for reuse. The main business risk is degraded network processing or availability on systems using affected kernels and XDP socket functionality. No public source here indicates active exploitation.
Executive priority
Treat as a planned kernel update priority for networking-intensive Linux systems. Escalate if vendors rate your distribution build higher, or if affected systems support critical packet processing. Current evidence does not support emergency active-exploitation handling.
Technical view
The issue follows commit b692bf9a7543, where list_node is reused for pool and free lists. Fragment deletion used list_del(), leaving node pointers initialized in a way that made list_empty() false. xp_free() could then skip returning buffers to the free list. Kernel stable fixes replace list_del() with list_del_init() in fragment paths.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions or backported commits and using xsk/AF_XDP paths. The CVE data lists Linux kernel versions and commits, but distribution package impact requires vendor mapping.
Exploitation context
The provided sources describe a buffer leak and kernel fix, not a complete attack path. KEV is false, and no cited source reports active exploitation. Practical impact appears availability-oriented, depending on workload and whether the affected xsk paths are reachable.
Researcher notes
The CVE record lacks CVSS, CWE, and detailed affected range semantics. Source evidence centers on the kernel commit rationale and stable backports. Validate exposure through exact vendor kernel source or changelog, because downstream distributions may backport the fix without changing major kernel versions.
Mitigation direction
Review kernel vendor advisories for CVE-2026-23326 applicability to your distributions.
Update to a kernel containing the relevant stable fix when available from your vendor.
Prioritize systems using AF_XDP, XDP sockets, or high-performance packet processing.
If patch timing is constrained, reduce reliance on affected xsk paths where operationally feasible.
Validation and detection
Inventory Linux kernel versions and vendor package builds across exposed systems.
Check whether AF_XDP or XDP socket functionality is used in production workloads.
Compare installed kernels against vendor advisories and the referenced stable commits.
Monitor for abnormal buffer exhaustion, network degradation, or kernel resource pressure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23326 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 25, 2026, 10:27 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.