CVE-2026-64244: drivers/base/memory: set mem->altmap after successful device registration
drivers/base/memory: set mem->altmap after successful device registration
Affected Software
Remediation
Event History
Frequently Asked Questions
What conditions are needed to trigger this issue?
The failure path is triggered when __add_memory_block() fails at xa_store(), such as under memory pressure. Cleanup then unregisters the device while mem->altmap is still set.
What access does an attacker need?
The supplied CVSS vector indicates local access and low privileges are required. No user interaction is required.
What is the expected security impact?
The rating indicates a high availability impact, with no confidentiality or integrity impact. The affected path can trigger WARN_ON(mem->altmap).
How can I mitigate the issue if it applies to my kernel?
A patch is available. No alternative workaround is provided in the available data.
How can I identify whether the failure has occurred?
Look for a WARN_ON(mem->altmap) warning associated with device cleanup after a failed memory-block registration. The described failure occurs when xa_store() fails during __add_memory_block().