Encrypted-device corruption via mutable O_DIRECT buffers
Published Apr 3, 2024 · Updated Aug 5, 2026
Data corruption in Linux dm-crypt allows local users to corrupt authenticated-encryption devices through concurrent O_DIRECT writes. dm-crypt encrypts caller-owned bio data in place, allowing userspace to change a buffer after tag computation and produce ciphertext with an invalid authentication tag. Exploitation requires local low-privilege access, dm-crypt authenticated encryption, and a concurrent write race; the bounded result is encrypted-device corruption.
Summary
What happened
Data corruption in Linux dm-crypt allows local users to corrupt authenticated-encryption devices through concurrent O_DIRECT writes. dm-crypt encrypts caller-owned bio data in place, allowing userspace to change a buffer after tag computation and produce ciphertext with an invalid authentication tag. Exploitation requires local low-privilege access, dm-crypt authenticated encryption, and a concurrent write race; the bounded result is encrypted-device corruption.
The record
- CVE
- CVE-2024-26763
- Published
- Apr 3, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1485
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.12
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <0dccbb93538fe89a86c6de31d4b1c8c560848eaa
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <1a4371db68a31076afbe56ecce34fbbe6c80c529
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <3c652f6fa1e1f9f02c3fbf359d260ad153ec5f90
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <43a202bd552976497474ae144942e32cc5f34d7e
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <50c70240097ce41fe6bce6478b80478281e4d0f7
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <64ba01a365980755732972523600a961c4266b75
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <d9e3763a505e50ba3bd22846f2a8db99429fb857
- Affected versionversion=ef43aa38063a6b2b3c6618e28ab35794f4f1fe29 <e08c2a8d27e989f0f5b0888792643027d7e691e6
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.
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