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,…
Does this matter?
Lower severity and a low EPSS score (0.11%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.11% probability · 2th percentile
- CISA KEV
- Not listed
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/059ac6252a63edf1cea79bf30bd860a8c264b62cPatch
- https://git.kernel.org/stable/c/22dc0d042f02ce82aa61422ea5f232628bfd9e9cPatch
- https://git.kernel.org/stable/c/6c25bf4e44a2b6a14332f952bba0974521f5b72dPatch
- https://git.kernel.org/stable/c/802e113cf120df7208e4c7e604950a85e87120a8Patch
- https://git.kernel.org/stable/c/a2b8d7827f48ee54a686cb80e4a1d0ff954ec42aPatch
- https://git.kernel.org/stable/c/bc3dd82a0ffd488bb902f4c69c3d28fd4088d973Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.