Microsoft security update for CVE-2024-43854
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43854. This page also shows what EchelonGraph holds for CVE-2024-43854, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 kernel 6.6.43.1-7 on Azure Linux 3.0
- azl3 kernel 6.6.47.1-1 on Azure Linux 3.0
- cbl2 kernel 5.15.164.1-1 on CBL Mariner 2.0
- cbl2 kernel 5.15.164.1-1 on CBL-Mariner 2.0
- cbl2 kernel 5.15.167.1-1 on CBL Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 5.15.167.1-1 |
| — | Security Update | 6.6.47.1-1 |
🧭 EchelonGraph on CVE-2024-43854
- EchelonGraph score
- 5.5 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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.
Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-43854, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).