CVE-2026-64244: Linux kernel · drivers/base/memory: set mem->altmap after successful device registration
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bc3dd82a0ffd488bb902f4c69c3d28fd4088d973 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:51 UTC
Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in bc3dd82a0ffd488bb902f4c69c3d28fd4088d973, a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a, 802e113cf120df7208e4c7e604950a85e87120a8 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users and administrators should update to the fixed versions identified by the provided commit hashes to resolve this issue.
Description
A vulnerability in the Linux kernel's memory management subsystem was fixed by changing when the mem->altmap field is set during device registration. Previously, if __add_memory_block() failed during memory pressure, device_unregister() would trigger memory_block_release() with mem->altmap still set, causing a kernel warning. The fix delays setting mem->altmap until after successful addition of the memory block.
References
- git.kernel.org/stable/c/802e113cf120df7208e4c7e604950a85e87120a8 (opens in a new tab)
- git.kernel.org/stable/c/22dc0d042f02ce82aa61422ea5f232628bfd9e9c (opens in a new tab)
- git.kernel.org/stable/c/6c25bf4e44a2b6a14332f952bba0974521f5b72d (opens in a new tab)
- git.kernel.org/stable/c/bc3dd82a0ffd488bb902f4c69c3d28fd4088d973 (opens in a new tab)
- git.kernel.org/stable/c/059ac6252a63edf1cea79bf30bd860a8c264b62c (opens in a new tab)
- git.kernel.org/stable/c/a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a (opens in a new tab)