Critical remote kernel vulnerability in the Linux kernel network driver (widely deployed OS/kernel); can enable remote code execution or widespread outages.
CVE-2026-72065
Linux kernel net/mana driver accepts forged RX lengths, enabling kernel memory corruption.
Is CVE-2026-72065 being exploited?
Not confirmed. CVE-2026-72065 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.73% probability of exploitation in the next 30 days.
How severe is CVE-2026-72065?
CVE-2026-72065 is rated Critical with a CVSS score of 9.8. 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-72065?
Yes. A fix has been recorded for CVE-2026-72065. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72065 affect?
CVE-2026-72065 affects Linux kernel (net/mana network driver), Hosts using impacted NICs that report RX CQE lengths. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72065?
Apply kernel security update immediately; isolate or block untrusted networks to affected hosts if patch delayed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers can send crafted NIC packets causing out‑of‑bounds kernel memory access, leading to crash, privilege escalation, or remote code execution.
Immediate action required
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < a631f82f89c76084ad5b2b9c043d3b391ffa56d8
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < d2568e64d01f480200063fadd67d6938f676c66f
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 2e276b14b6d378372bf0152df89286cbe7632fb0
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 6080189291d958604dcefe513a13900835ac982f
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 6d13eaa13341a8f80aaf86f78591e1b1d393711d
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 282c5214ca4eb3799158c76782646e86d2945d1b
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 2e2a83b4998af4384e677d3b2ac08565274279bf
- affected5.13
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.