CVE-2022-50889
Description
In the Linux kernel, the following vulnerability has been resolved:
dm integrity: Fix UAF in dm_integrity_dtr()
Dm_integrity also has the same UAF problem when dm_resume() and dm_destroy() are concurrent.
Therefore, cancelling timer again in dm_integrity_dtr().
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A use-after-free (UAF) vulnerability in the Linux kernel's dm-integrity driver occurs when dm_resume() and dm_destroy() run concurrently, fixed by cancelling the timer in dm_integrity_dtr().
Vulnerability
Overview
CVE-2022-50889 is a use-after-free (UAF) vulnerability in the Linux kernel's device-mapper integrity (dm-integrity) target. The bug arises when the dm_resume() and dm_destroy() operations are executed concurrently, leading to a race condition where the integrity device's timer can be freed while still in use. This is a classic UAF scenario that can result in memory corruption or arbitrary code execution.
Exploitation
Context
To trigger the vulnerability, an attacker must be able to issue concurrent dm_resume() and dm_destroy() calls on the same dm-integrity device. This requires local access to the system and the ability to interact with the device-mapper subsystem, typically through privileged operations (e.g., root or CAP_SYS_ADMIN). The race window is small, but a timing-dependent condition that can be exploited by carefully orchestrating the two operations.
Impact
If successfully exploited, the UAF can lead to system instability, denial of service (kernel crash), or potentially privilege escalation if an attacker can control the freed memory. The vulnerability is rated with a CVSS score of 7.0 (High), reflecting high severity due to the potential for local privilege escalation.
Mitigation
The fix, introduced in the Linux kernel stable tree, ensures that the timer is cancelled again in dm_integrity_dtr() to prevent the race condition [1][2][3]. Users should apply the latest kernel updates from their distribution or backport the specific commit to mitigate the issue. No workarounds are not available; patching is required.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
6792e51aac376a506b5c927579215b25f2e109f8e1e54a3a4b6c93cd61afaf50cb2cbabd6Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
6- git.kernel.org/stable/c/792e51aac376cfb5bd527c2a30826223b82dd177nvd
- git.kernel.org/stable/c/9215b25f2e105032114e9b92c9783a2a84ee8af9nvd
- git.kernel.org/stable/c/9f8e1e54a3a424c6c4fb8742e094789d3ec91e42nvd
- git.kernel.org/stable/c/a506b5c92757b034034ef683e667bffc456c600bnvd
- git.kernel.org/stable/c/b6c93cd61afab061d80cc842333abca97b289774nvd
- git.kernel.org/stable/c/f50cb2cbabd6c4a60add93d72451728f86e4791cnvd
News mentions
0No linked articles in our index yet.