CVE-2026-64018
Linux kernel 'mana' driver OOB index leads to kernel memory corruption in Confidential VMs.
Is CVE-2026-64018 being exploited?
Not confirmed. CVE-2026-64018 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-64018?
CVE-2026-64018 is rated Critical with a CVSS score of 9.3. 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-64018?
Yes. A fix has been recorded for CVE-2026-64018. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64018 affect?
CVE-2026-64018 affects Linux kernel (net/mana driver), Confidential VMs (SEV-SNP, TDX), Systems using DMA-capable NICs on affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64018?
Apply vendor/kernel update that patches the mana driver immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Host/hardware-controlled DMA WQE can cause out-of-bounds kernel access, enabling memory corruption and potential privilege escalation or guest compromise.
Immediate action required
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 5ddc715324badd7f2641bc177db1d027b402adae
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < ff1d5af207bcea857d45fe81505f1bc4b29eaef0
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 01f7f893d5e1baae995beeb86cd0f3e6bb2a3b01
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 763a372d344fb12fae566d36ddb46e92454ad58c
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < fa627a5eaa83fc0261f44ef3769693b886ca6e27
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < 355e9f2b2a7887ca38100127989af3e422ba71d0
- affected>= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and < b809d0409991b75a6cff846a5ac27c3062953f84
- 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.