CVE-2026-64244
In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: set mem->altmap after successful device registration If __add_memory_block() fails at xa_store() (under memory pressure for example), device_unregister() is called, which eventually triggers memory_block_release() with mem->altmap still set, causing a WARN_ON(mem->altmap). This was triggered by modifying virtio-mem driver. Fix this by delaying the assignment of mem->altmap until after __add_memory_block() has succeeded.
Affected versions
Linux kernel versions
6.6
and later are affected. Fixed in
6.6.144,
6.12.95,
6.18.37,
7.0.14,
7.1.2,
7.2-rc1
and their respective stable series.
References
6 totalFrequently asked questions
-
What is CVE-2026-64244?
CVE-2026-64244 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.6 onward and has been patched in 6.6.144, 6.12.95, 6.18.37 and others. CVE-2026-64244 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-64244?
Yes. CVE-2026-64244 has been patched. Fixed versions include 6.6.144, 6.12.95, 6.18.37 and others. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64244 actively exploited?
No. CVE-2026-64244 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.