CVE-2026-64104
Linux SEV guest kernel flaw may leave pages unencrypted, risking guest memory leakage.
Is CVE-2026-64104 being exploited?
Not confirmed. CVE-2026-64104 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.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-64104?
CVE-2026-64104 is rated High with a CVSS score of 8.7. 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-64104?
Yes. A fix has been recorded for CVE-2026-64104. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64104 affect?
CVE-2026-64104 affects Linux kernel (SEV guest support), AMD SEV/SNP-enabled VMs, Cloud hosts offering AMD SEV VMs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64104?
Apply kernel security updates, reboot affected VMs, rotate exposed secrets/keys
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Host/hypervisor or privileged attacker can read guest memory if pages remain unencrypted after set_memory_* failure, exposing secrets.
Patch when possible
- affected>= 3e385c0d6ce88ac9916dcf84267bd5855d830748 and < bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0
- affected>= 3e385c0d6ce88ac9916dcf84267bd5855d830748 and < 3d0cd0065deeb054b4b29236432e851806b7cc81
- affected>= 3e385c0d6ce88ac9916dcf84267bd5855d830748 and < fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf
- affected0b16521f95c875e79d657cb8d6911c15080dbb80
- affected>= 6.13.8 and < 6.14
- affected6.14
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.