CVE-2026-64244
drivers/base/memory: set mem->altmap after successful device registration
Description
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.
INFO
Published Date :
July 24, 2026, 4:16 p.m.
Last Modified :
July 24, 2026, 4:16 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64244
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the resolved version.
- Apply the provided patch to the kernel source.
- Recompile and install the modified kernel.
- Reboot the system with the updated kernel.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64244.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64244 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64244
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64244 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64244 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 24, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '1a8c64e110435e44e71bcd50a75663174b575f22', 'lessThan': '802e113cf120df7208e4c7e604950a85e87120a8', 'versionType': 'git'}, {'status': 'affected', 'version': '1a8c64e110435e44e71bcd50a75663174b575f22', 'lessThan': '22dc0d042f02ce82aa61422ea5f232628bfd9e9c', 'versionType': 'git'}, {'status': 'affected', 'version': '1a8c64e110435e44e71bcd50a75663174b575f22', 'lessThan': '6c25bf4e44a2b6a14332f952bba0974521f5b72d', 'versionType': 'git'}, {'status': 'affected', 'version': '1a8c64e110435e44e71bcd50a75663174b575f22', 'lessThan': 'bc3dd82a0ffd488bb902f4c69c3d28fd4088d973', 'versionType': 'git'}, {'status': 'affected', 'version': '1a8c64e110435e44e71bcd50a75663174b575f22', 'lessThan': '059ac6252a63edf1cea79bf30bd860a8c264b62c', 'versionType': 'git'}, {'status': 'affected', 'version': '1a8c64e110435e44e71bcd50a75663174b575f22', 'lessThan': 'a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a', 'versionType': 'git'}], 'programFiles': ['drivers/base/memory.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.6'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.6', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.144', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.95', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.37', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.14', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1.2', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/base/memory.c'], 'defaultStatus': 'affected'}] Added Description 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. Added Reference https://git.kernel.org/stable/c/059ac6252a63edf1cea79bf30bd860a8c264b62c Added Reference https://git.kernel.org/stable/c/22dc0d042f02ce82aa61422ea5f232628bfd9e9c Added Reference https://git.kernel.org/stable/c/6c25bf4e44a2b6a14332f952bba0974521f5b72d Added Reference https://git.kernel.org/stable/c/802e113cf120df7208e4c7e604950a85e87120a8 Added Reference https://git.kernel.org/stable/c/a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a Added Reference https://git.kernel.org/stable/c/bc3dd82a0ffd488bb902f4c69c3d28fd4088d973