Host crash via repeated failed cache resume
Published Jun 18, 2025 · Updated May 11, 2026
Reachable assertion in affected Linux kernel releases allows local users to crash the host by retrying a failed dm-cache device resume. The device-mapper cache resume path permits another resume after corrupted mapping metadata leaves the SMQ policy object partly initialized, causing smq_load_mapping to reach BUG_ON while reloading mappings. Triggering the fault requires local access sufficient to alter cache metadata and resume the device twice; the resulting kernel oops interrupts the host.
Summary
What happened
Reachable assertion in affected Linux kernel releases allows local users to crash the host by retrying a failed dm-cache device resume. The device-mapper cache resume path permits another resume after corrupted mapping metadata leaves the SMQ policy object partly initialized, causing smq_load_mapping to reach BUG_ON while reloading mappings. Triggering the fault requires local access sufficient to alter cache metadata and resume the device twice; the resulting kernel oops interrupts the host.
The record
- CVE
- CVE-2025-38066
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.2
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <00586b78eeb7c626a14ca13453a1631f88a7cf36
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <025c8f477625eb39006ded650e7d027bcfb20e79
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <3986ef4a9b6a0d9c28bc325d8713beba5e67586f
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <5da692e2262b8f81993baa9592f57d12c2703dea
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <c5356a5e80442131e2714d0d26bb110590e4e568
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <c614584c2a66b538f469089ac089457a34590c14
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <cc80a5cc520939d0a7d071cc4ae4b3c55ef171d0
- Affected versionversion=66a636356647a9be8885c2ce2948de126577698a <f3128e3074e8af565cc6a66fe3384a56df87f803
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.
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