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.
References
Configurations
No configuration.
History
16 Sep 2026, 15:18
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.8 |
Information
Published : 2026-09-16 11:17
Updated : 2026-09-17 10:17
NVD link : CVE-2026-89997
Mitre link : CVE-2026-89997
CVE.ORG link : CVE-2026-89997
JSON object : View
Products Affected
No product.
CWE
No CWE.
