In the Linux kernel, the following vulnerability has been resolved:
net: fix skb length accounting after generic XDP frag adjustment
Generic XDP exposes non-linear skb fragments through an xdp_buff. If an
XDP program adjusts the fragment area, bpf_prog_run_generic_xdp() copies
xdp_frags_size back to skb->data_len but leaves skb->len containing the
old fragment contribution.
After a fragment shrink, this makes skb_headlen() larger than the actual
linear area. In the reproduced UDP receive path, __skb_datagram_iter()
copied 1024 bytes past the actual linear tail to userspace, starting at
struct skb_shared_info. The copied bytes included the affected skb's
nr_frags, xdp_frags_size and a kernel pointer from
skb_shinfo(skb)->frags[0]. Real packet data was displaced by the same
amount and truncated at the end.
Subtract the old data_len before replacing it and add the new data_len
afterwards, keeping skb->len and skb->data_len synchronized.
A 60000-byte UDP datagram on a veth pair with MTU 64000 was shortened by
1024 bytes from its fragment area. Before the fix, all 10 runs produced
corrupted payloads. After the fix, all 10 runs matched the expected
payload exactly.
Security readout for executives and security teams
Plain-English summary
CVE-2026-74665 is a critical Linux networking flaw involving generic XDP packet processing. Incorrect packet-length accounting can expose adjacent kernel memory, including a kernel pointer, to receiving user space and corrupt or truncate legitimate packet data. Risk is highest where affected kernels run generic XDP programs that adjust fragmented packet data.
Executive priority
Treat this as an urgent patch-validation issue for XDP-enabled Linux systems because the documented failure exposes kernel memory and corrupts network data. Accelerate vendor confirmation and remediation, but avoid claiming an active attack campaign: none is supported by the supplied evidence.
Technical view
After generic XDP changes an skb fragment area, bpf_prog_run_generic_xdp() updates skb->data_len without correctly recalculating skb->len. Following a fragment shrink, later UDP receive handling can read beyond the actual linear packet tail. The documented reproduction disclosed skb metadata and a kernel pointer while displacing and truncating packet data.
Likely exposure
The record identifies Linux as affected and lists version identifiers 6.9, 0, 6.12.104, 6.18.45, 7.1.9, and 7.2. Practical exposure also requires the relevant generic XDP fragment-adjustment path. Distribution kernels and appliances may contain backports, so version strings alone are insufficient; obtain vendor-specific affected and fixed package mappings.
Exploitation context
The supplied CVSS vector describes network reachability, low complexity, no privileges, and no user interaction. However, CISA KEV status is false, and the supplied sources do not report active exploitation or a public exploit. Evidence is limited to a controlled kernel reproduction that consistently produced memory disclosure and payload corruption before the fix.
Researcher notes
The fix synchronizes skb->len and skb->data_len by removing the old fragment contribution before adding the new value. The maintainer reproduction produced corrupted UDP payloads in every pre-fix run and correct payloads in every post-fix run. The exposed bytes included fragment metadata and a kernel pointer. Exact distribution exposure remains vendor-dependent.
Mitigation direction
Check Linux distribution or appliance vendor guidance for branch-specific affected and fixed packages.
Apply the vendor-approved kernel update containing a referenced stable fix or equivalent backport.
Prioritize XDP-enabled network systems while vendor package mappings are being confirmed.
Validation and detection
Inventory running kernels and identify systems using generic XDP with fragmented packet processing.
Compare each kernel package against vendor advisories, not only upstream version numbers.
Verify the running kernel contains a referenced stable fix or vendor-equivalent backport.
After updating, confirm the corrected kernel is active and test affected XDP and UDP workflows.
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-74665 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
5Source 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.