CVE-2024-43854
block: initialize integrity buffer to zero before writing it to media
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: block: initialize integrity buffer to zero before writing it to media Metadata added by bio_integrity_prep is using plain kmalloc, which leads to random kernel memory being written media. For PI metadata this is limited to the app tag that isn't used by kernel generated metadata, but for non-PI metadata the entire buffer leaks kernel memory. Fix this by adding the __GFP_ZERO flag to allocations for writes.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.27
References 8
git.kernel.org
- stable/c/9f4af4cf08f9a0329ade3d938f55d2220c40d0a6
- stable/c/129f95948a96105c1fad8e612c9097763e88ac5f
- stable/c/3fd11fe4f20756b4c0847f755a64cd96f8c6a005
- stable/c/cf6b45ea7a8df0f61bded1dc4a8561ac6ad143d2
- stable/c/d418313bd8f55c079a7da12651951b489a638ac1
- stable/c/23a19655fb56f241e592041156dfb1c6d04da644
- stable/c/ebc0e91ba76dc6544fff9f5b66408b1982806a00
- stable/c/899ee2c3829c5ac14bfc7d3c4a5846c0b709b78f