Service interruption via unbalanced DMA clock cleanup
Published May 1, 2025 · Updated May 23, 2026
Resource leakage in the Linux kernel mv_xor_v2 DMA driver allows local users to interrupt service by repeatedly removing the device. The mv_xor_v2_remove() path omits clk_disable_unprepare() after probe enables the clock with clk_prepare_enable(), so device removal leaves the clock resource enabled. Reachability requires local access and removal of a Marvell XOR v2 DMA device; published assessments report availability impact only, not data access or modification.
Summary
What happened
Resource leakage in the Linux kernel mv_xor_v2 DMA driver allows local users to interrupt service by repeatedly removing the device. The mv_xor_v2_remove() path omits clk_disable_unprepare() after probe enables the clock with clk_prepare_enable(), so device removal leaves the clock resource enabled. Reachability requires local access and removal of a Marvell XOR v2 DMA device; published assessments report availability impact only, not data access or modification.
The record
- CVE
- CVE-2022-49861
- Published
- May 1, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2299285fb1819ef8459c116fd1eafe1458bb9ca1 <4b6641c3a2ba95ddcfecec263b4a5e572a4b0641
- Affected versionversion=3bdcced41936b054470639c6a76ae033df1074e3 <04f2cc56d80a1ac058045a7835c5bfd910f17863
- Affected versionversion=3cd2c313f1d618f92d1294addc6c685c17065761 <081195d17a0c4c636da2b869bd5809d42e8cbb13
- Affected versionversion=3cd2c313f1d618f92d1294addc6c685c17065761 <0b7ee3d50f32d277bf024b4ddb4de54da43a3025
- Affected versionversion=3cd2c313f1d618f92d1294addc6c685c17065761 <1d84887327659c58a6637060ac8c50c3a952a163
- Affected versionversion=3cd2c313f1d618f92d1294addc6c685c17065761 <20479886b40c0ed4864a5fc8490a1f6b70cccf1b
- Affected versionversion=3cd2c313f1d618f92d1294addc6c685c17065761 <992e966caf57e00855edbd79f19d911809732a69
- Affected versionversion=3cd2c313f1d618f92d1294addc6c685c17065761 <a1cb72e20a64a3c83f9b4ee993fbf97e4c1d7714
- Affected versionversion=4.14.45 <4.14.300
- Affected versionversion=4.16
- Affected versionversion=4.9.104 <4.9.334
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo