CVE-2026-89997: dm: fix resume-vs-remove race
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1ede2bce2bd640605df83db1356fd727159bc9ed, 2.6.36, 36177beff2a9df035991ad8d16ccf8d363ed93ee.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1ede2bce2bd640605df83db1356fd727159bc9ed, 2.6.36, 36177beff2a9df035991ad8d16ccf8d363ed93ee or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: dm: fix resume-vs-remove race If the user issues the resume ioctl and the remove ioctl at the same time, it may be possible that the device is resumed after it is suspended in __dm_destroy. The result is that the table is destroyed without calling the postsuspend method. Dm targets expect that they may be removed only after the postsuspend method method was called. If we break this expectation, it can cause misbehavior in various targets. For example - in the dm-integrity target, the reboot notifier is not unregistered, leading to use-after-free. Fix this bug by refusing to resume if the device is being destroyed.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 305b06f7334dd43bc952b525d7232f4cae7c3818, 2.6.36affected
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 9757367bcf1d5d2c50b94d005abca21f3eedd7c3affected · git
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 1ede2bce2bd640605df83db1356fd727159bc9edaffected · git
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 3f04e6520d9a53adb1d1daf4dc5d31a60fc77d1faffected · git
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 94f3d399c1ddba763c1c5a6501f7375d533d789faffected · git
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 3b59530b14fde693e41d8e39bc326df6cbf07b76affected · git
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 36177beff2a9df035991ad8d16ccf8d363ed93eeaffected · git
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 94380ecd5ff9b2a2b9f6e8a0b5c465159ccfaf71affected · git
- 3f77316de0ec0fd208467fbee8d9edc70e2c73b2 and later · before 44b43ec132f1cf3275ecc182d0c82f50c3c4c3d5affected · git
- 2.6.35.4 and later · before 2.6.36affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89995Sep 16, 2026 · dma-direct: return struct page from dma_direct_alloc_from_pool()35Monitor
- ← EarlierCVE-2026-89996Sep 16, 2026 · dma-buf: dma-heap: don't publish fd before copy_to_user() succeeds0Monitor
- Later →CVE-2026-89998Sep 16, 2026 · dm: fix race when loading and unloading a table31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1ede2bce2bd640605df83db1356fd727159bc9ed | Vendor (CNA) |
| Linux Linux | 2.6.36 | Vendor (CNA) |
| Linux Linux | 36177beff2a9df035991ad8d16ccf8d363ed93ee | Vendor (CNA) |
| Linux Linux | 3b59530b14fde693e41d8e39bc326df6cbf07b76 | Vendor (CNA) |
| Linux Linux | 3f04e6520d9a53adb1d1daf4dc5d31a60fc77d1f | Vendor (CNA) |
| Linux Linux | 44b43ec132f1cf3275ecc182d0c82f50c3c4c3d5 | Vendor (CNA) |
| Linux Linux | 94380ecd5ff9b2a2b9f6e8a0b5c465159ccfaf71 | Vendor (CNA) |
| Linux Linux | 94f3d399c1ddba763c1c5a6501f7375d533d789f | Vendor (CNA) |
| Linux Linux | 9757367bcf1d5d2c50b94d005abca21f3eedd7c3 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/36177beff2a9df035991ad8d16ccf8d363ed93ee
- git.kernel.org/stable/c/3b59530b14fde693e41d8e39bc326df6cbf07b76
- git.kernel.org/stable/c/3f04e6520d9a53adb1d1daf4dc5d31a60fc77d1f
- git.kernel.org/stable/c/44b43ec132f1cf3275ecc182d0c82f50c3c4c3d5
- git.kernel.org/stable/c/94380ecd5ff9b2a2b9f6e8a0b5c465159ccfaf71
- git.kernel.org/stable/c/94f3d399c1ddba763c1c5a6501f7375d533d789f
- git.kernel.org/stable/c/9757367bcf1d5d2c50b94d005abca21f3eedd7c3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.