In the Linux kernel, the following vulnerability has been resolved:
xsk: Harden userspace-supplied xdp_desc validation
Turned out certain clearly invalid values passed in xdp_desc from
userspace can pass xp_{,un}aligned_validate_desc() and then lead
to UBs or just invalid frames to be queued for xmit.
desc->len close to ``U32_MAX`` with a non-zero pool->tx_metadata_len
can cause positive integer overflow and wraparound, the same way low
enough desc->addr with a non-zero pool->tx_metadata_len can cause
negative integer overflow. Both scenarios can then pass the
validation successfully.
This doesn't happen with valid XSk applications, but can be used
to perform attacks.
Always promote desc->len to ``u64`` first to exclude positive
overflows of it. Use explicit check_{add,sub}_overflow() when
validating desc->addr (which is ``u64`` already).
bloat-o-meter reports a little growth of the code size:
add/remove: 0/0 grow/shrink: 2/1 up/down: 60/-16 (44)
Function old new delta
xskq_cons_peek_desc 299 330 +31
xsk_tx_peek_release_desc_batch 973 1002 +29
xsk_generic_xmit 3148 3132 -16
but hopefully this doesn't hurt the performance much.
Security readout for executives and security teams
Plain-English summary
A locally accessible Linux kernel flaw lets a low-privileged process supply malformed AF_XDP transmit descriptors that bypass validation. Integer wraparound may trigger undefined kernel behavior or queue invalid network frames, creating potential confidentiality, integrity, and availability impact. Ordinary valid AF_XDP applications do not trigger the issue.
Executive priority
Treat this as a high-priority kernel update for multi-user hosts, shared compute, and systems running less-trusted local workloads. It is not described as remotely exploitable, and active exploitation is unconfirmed, so prioritize according to local-access exposure rather than initiating an emergency internet-wide response.
Technical view
AF_XDP descriptor validation mishandles extreme xdp_desc length or address values when TX metadata is enabled. Addition or subtraction can overflow, allowing invalid descriptors through validation. The kernel fix promotes length calculations to 64 bits and adds explicit overflow checks for address arithmetic.
Likely exposure
Exposure is most likely on affected Linux kernels where local users or workloads can submit AF_XDP transmit descriptors. The supplied version data identifies 6.8, 6.12.54, 6.17.4, and 6.18, but its precise range semantics are unclear; confirm status with the kernel or distribution vendor.
Exploitation context
The CVSS assessment is 7.8 and describes local, low-complexity exploitation requiring low privileges and no user interaction. The source says malformed descriptors can be used for attacks, but provides no evidence of exploitation in the wild. This CVE is not listed as KEV in the supplied bundle.
Researcher notes
The flaw concerns arithmetic overflow in xp aligned and unaligned descriptor validation. Extreme length values can wrap during metadata addition; low addresses can underflow during metadata subtraction. Resulting descriptors may cause undefined behavior or invalid transmission. The sources provide no CWE, proof of exploitation, or detailed impact demonstration.
Mitigation direction
Apply a vendor-supported kernel update containing the relevant stable fix.
Check distribution advisories for affected and fixed package versions.
Prioritize systems permitting untrusted local workloads or AF_XDP access.
Restrict unnecessary local access and AF_XDP-capable workloads until patched.
Validation and detection
Record running kernel and distribution package versions.
Compare installed packages with the distribution vendor's CVE guidance.
Identify workloads using AF_XDP, especially transmit metadata features.
Confirm the installed kernel contains the applicable linked stable fix.
Retest affected networking workloads after updating and rebooting.
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-2025-40159 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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.