Kernel-memory disclosure via uninitialized integrity metadata
Published Aug 17, 2024 · Updated May 11, 2026
Kernel-memory disclosure in the Linux block layer allows local users to recover uninitialized data written into integrity metadata. bio_integrity_prep allocates write-side integrity metadata with plain kmalloc, leaving prior kernel heap contents in the buffer before it is written to media. Exploitation requires local low-privileged access and a storage path using integrity metadata; non-PI metadata exposes the entire buffer.
Summary
What happened
Kernel-memory disclosure in the Linux block layer allows local users to recover uninitialized data written into integrity metadata. bio_integrity_prep allocates write-side integrity metadata with plain kmalloc, leaving prior kernel heap contents in the buffer before it is written to media. Exploitation requires local low-privileged access and a storage path using integrity metadata; non-PI metadata exposes the entire buffer.
The record
- CVE
- CVE-2024-43854
- Published
- Aug 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2024CVE 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=2.6.27
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <129f95948a96105c1fad8e612c9097763e88ac5f
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <23a19655fb56f241e592041156dfb1c6d04da644
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <3fd11fe4f20756b4c0847f755a64cd96f8c6a005
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <899ee2c3829c5ac14bfc7d3c4a5846c0b709b78f
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <9f4af4cf08f9a0329ade3d938f55d2220c40d0a6
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <cf6b45ea7a8df0f61bded1dc4a8561ac6ad143d2
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <d418313bd8f55c079a7da12651951b489a638ac1
- Affected versionversion=7ba1ba12eeef0aa7113beb16410ef8b7c748e18b <ebc0e91ba76dc6544fff9f5b66408b1982806a00
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