Data loss via premature dm-cache cleanliness check
Published Jun 24, 2026 · Updated Jun 24, 2026
Data corruption in Linux Kernel dm-cache allows local users to lose cached data during a passthrough-mode transition with dirty mappings. The cleanliness check runs during table creation instead of preresume, so an LVM-preloaded table can pass while metadata updates create dirty mappings. Exploitation requires a writeback cache, an inactive passthrough table, a concurrent dirtying write, and permission to resume the table; stale mappings can destroy data.
Summary
What happened
Data corruption in Linux Kernel dm-cache allows local users to lose cached data during a passthrough-mode transition with dirty mappings. The cleanliness check runs during table creation instead of preresume, so an LVM-preloaded table can pass while metadata updates create dirty mappings. Exploitation requires a writeback cache, an inactive passthrough table, a concurrent dirtying write, and permission to resume the table; stale mappings can destroy data.
The record
- CVE
- CVE-2026-53061
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1485
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <01b22656d8a68dbeae59f8b80866e7b11936b20a
- Affected versionversion=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <12105c7f18375d7615dad7605d89eadae7eb12a6
- Affected versionversion=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <1443c32f24d6d8bcdf4beceef2afc09290b98717
- Affected versionversion=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <21c503d60a257e54ca3ac58e2721bd24501d5bde
- Affected versionversion=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <322586745bd1a0e5f3559fd1635fdeb4dbd1d6b8
- Affected versionversion=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <5c98a3f1d7a554c9e920aa31daf92af6b5bbb8cc
- Affected versionversion=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <bd5a2c1018938e6b32670728bdb32a3f0efff00f
- Affected versionversion=2ee57d587357f0d752af6c2e3e46434a74b1bee3 <c2e86f647561fcf5e1c6eba7d75e9e0c4299c94d
- Affected versionversion=3.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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