Live › vulnerability › CVE-2026-99036
Go to dashboardA race in the Linux kernel device-mapper resume path can read freed memory when two ioctls on the same device swap tables concurrently. The sources say only root can trigger it and that the kernel maintainers do not consider it a security bug.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems with Linux device-mapper in use, such as LVM or dm-crypt volumes, on a kernel without the fix. Per the sources only root can trigger it, and common tools like lvm and cryptsetup do not issue the ioctls concurrently, so exposure to an attacker is low. The sources do not name affected kernel version ranges.
No product ranges from the sources yet.
uname -r to see the running kernel versionEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
dm: fix reading free memory in do_resume
When do_resume calls dm_table_get_mode(new_map), the call is done without holding any locks (it only holds a reference to the md). It may be possible that another concurrent ioctl on the same device will swap table after dm_swap_table and before dm_table_get_mode. In this case, dm_table_get_mode(new_map) reads freed memory.
This race condition was triggered by syzbot.
This commit fixes the race by reading mode of the new table before dm_swap_table. Note that new_map is also passed to dm_ima_need_measure, but this function doesn't attempt to dereference it, so this call should be safe.
Note that this is not a security bug because only root can trigger it and the commonly used tools such as lvm or cryptsetup do not call the ioctls concurrently, so that they can't trigger it acceidentally.
This page as .md · .json · in your agent: get_signal("CVE-2026-99036")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.