Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
🚨*CVE* 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(… https://www.cve.org/CVERecord?id=CVE-2026-64244 ----- Traducción: CVE-2026-64244 En … http://infoflow.cloud`
Post summary
The post announces that CVE‑2026‑64244 has been fixed in the Linux kernel’s memory driver, referencing the patch location.
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(… https://www.cve.org/CVERecord?id=CVE-2026-64244
Post summary
This post announces that CVE-2026-64244 has been fixed in the Linux kernel, indicating a patch is available, with no evidence of exploitation or PoC.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| OS | linux | linux_kernel | - | - | - |