CVE-2026-99036: Linux kernel · dm: fix reading free memory in do_resume
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e3bf232c913b7e0103d323f15e6342d37cb1b357 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e3bf232c913b7e0103d323f15e6342d37cb1b357, c9417c1c5269e2bd0570fbe53e4ec03a8d31f008, 301691c32b8ad023e3316d5dbb6a8cf52d47b0dc +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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 commits listed in the established facts. Users should update to a kernel version including these fixes to resolve the race condition. Since only root can trigger this and common tools do not cause the race, no additional mitigation is necessary beyond applying the official fix.
Description
A race condition in the Linux kernel device mapper (dm) subsystem was fixed where reading free memory could occur during the do_resume operation. This happens because dm_table_get_mode is called without holding locks, allowing a concurrent ioctl to swap the table and cause dm_table_get_mode to read freed memory. The issue was triggered by syzbot and fixed by reading the mode before swapping the table. This is not considered a security bug since only root can trigger it and common tools do not invoke the relevant ioctls concurrently.
References
- git.kernel.org/stable/c/281f68d6cf8acb2547ebf0a849b8beae8fb0ec3c (opens in a new tab)
- git.kernel.org/stable/c/2c96d1a8324e7736e0f8a5790ecf39d36c2c4a82 (opens in a new tab)
- git.kernel.org/stable/c/e3bf232c913b7e0103d323f15e6342d37cb1b357 (opens in a new tab)
- git.kernel.org/stable/c/301691c32b8ad023e3316d5dbb6a8cf52d47b0dc (opens in a new tab)
- git.kernel.org/stable/c/c9417c1c5269e2bd0570fbe53e4ec03a8d31f008 (opens in a new tab)