Answer in brief
CVE-2026-99036 records a Unknown severity vulnerability in dm: fix reading free memory in do_resume. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <281f68d6cf8acb2547ebf0a849b8beae8fb0ec3c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2c96d1a8324e7736e0f8a5790ecf39d36c2c4a82 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e3bf232c913b7e0103d323f15e6342d37cb1b357 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <301691c32b8ad023e3316d5dbb6a8cf52d47b0dc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c9417c1c5269e2bd0570fbe53e4ec03a8d31f008 || >=0 <6.6.160 || >=0 <6.12.113 || >=0 <6.18.57 || >=0 <7.2.11 | 281f68d6cf8acb2547ebf0a849b8beae8fb0ec3c, 2c96d1a8324e7736e0f8a5790ecf39d36c2c4a82, e3bf232c913b7e0103d323f15e6342d37cb1b357, 301691c32b8ad023e3316d5dbb6a8cf52d47b0dc, c9417c1c5269e2bd0570fbe53e4ec03a8d31f008, 6.6.160, 6.12.113, 6.18.57, 7.2.11 |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.