CVE-2026-64368
Linux kernel allocator bug can return uninitialized memory, breaking __GFP_ZERO guarantees
Is CVE-2026-64368 being exploited?
Not confirmed. CVE-2026-64368 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.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-64368?
CVE-2026-64368 is rated High with a CVSS score of 8.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-64368?
Yes. A fix has been recorded for CVE-2026-64368. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64368 affect?
CVE-2026-64368 affects Linux kernel (SLAB/SLUB allocators), Multiple Linux distributions using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64368?
Apply vendor kernel updates and reboot affected hosts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allocator may return uninitialized kernel memory on kmalloc/krealloc, enabling information disclosure or facilitating local exploit paths.
Patch when possible
- affected>= 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 and < 6256899c3a34674bba6076884aedbba49fc695e4
- affected>= 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 and < 7e706d50fa119eead6376bf0ef973e8d73a96030
- affected>= 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 and < 2382971aaaef5bf85a651234c64906f59580b8be
- affected>= 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 and < 0d18ccef142f04433dfb2a0c120cf223d2b8a42c
- affected>= 9ce67395f5a0cdec6ce152d26bfda13b98b25c01 and < 648927ceb84021a25a0fbd5673740956f318d534
- affected6.2
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.