Skip to content
Systems

CVE-2026-74665

9.1
Critical
EPSS 0.37%Patch availableAug 25, 2026

Linux kernel XDP skb fragment accounting bug causes data corruption and kernel pointer leak.

common questions

Is CVE-2026-74665 being exploited?

Not confirmed. CVE-2026-74665 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-74665?

CVE-2026-74665 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74665?

Yes. A fix has been recorded for CVE-2026-74665. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74665 affect?

CVE-2026-74665 affects Linux kernel (XDP/generic_xdp skb handling). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74665?

Install vendor kernel updates; restrict untrusted UDP/XDP traffic until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (XDP/generic_xdp skb handling)
impact

Crafted fragmented UDP packets with XDP adjustments can cause userspace to over-read kernel memory (pointer leak) and truncate/corrupt UDP payloads; info disclosure and data integrity loss.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= e6d5dbdd20aa6a86974af51deb9414cd2e7794cb and < 72468efcc089782fa047afddd10856b11a14ef5b
  • affected>= e6d5dbdd20aa6a86974af51deb9414cd2e7794cb and < 5f30f9c302cea1f2ebf97abe574c1826544223d7
  • affected>= e6d5dbdd20aa6a86974af51deb9414cd2e7794cb and < ea1ccd6d1c6370868e3b032a3fc575b9c397f2e1
  • affected>= e6d5dbdd20aa6a86974af51deb9414cd2e7794cb and < 33f2b2eb33d666ecac68031e0f31424fb70528db
  • affected6.9
vendor says fixed in< 6.9, >= 6.12.104 and <= 6.12.*, >= 6.18.45 and <= 6.18.*, >= 7.1.9 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free