CVE-2024-43854
block: initialize integrity buffer to zero before writing it to media
Reported by linux · Published August 17, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-devel | Amazon Linux | 4.14.355-271.569.amzn2 |
| kernel-livepatch-6.1.106-116.188 | Amazon Linux | 1.0-0.amzn2023 |
| kernel-libbpf | Amazon Linux | 6.1.106-116.188.amzn2023 |
| kernel-tools-devel | Amazon Linux | 6.1.106-116.188.amzn2023, 4.14.355-271.569.amzn2 |
| kernel-livepatch-4.14.355-271.569 | Amazon Linux | 1.0-0.amzn2 |
| perf | Amazon Linux | 6.1.106-116.188.amzn2023, 4.14.355-271.569.amzn2 |
| python-perf | Amazon Linux | 4.14.355-271.569.amzn2 |
| Linux | Linux | d418313bd8f55c079a7da12651951b489a638ac1, cf6b45ea7a8df0f61bded1dc4a8561ac6ad143d2, 3fd11fe4f20756b4c0847f755a64cd96f8c6a005, 129f95948a96105c1fad8e612c9097763e88ac5f |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b, 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b, 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b |
| Linux | Linux | 2.6.27, 0, 4.19.322 |
| amazon:2 | kernel-devel | 0 |
| amazon:2023 | kernel-livepatch-6.1.106-116.188 | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2 | kernel-tools-devel | 0 |
| amazon:2 | kernel-livepatch-4.14.355-271.569 | 0 |
| amazon:2023 | perf | 0 |
| amazon:2 | python-perf | 0 |
| amazon:2 | perf | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| Linux | Linux | 0, 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b, 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2 | kernel | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel | 0 |
…and 6 more
Timeline
- Aug 17, 2024 CVE Published
- Aug 18, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (7 in total, the first dated here)
- Jan 5, 2026 Security Advisory (163 in total, the first dated here)
- Mar 30, 2026 Distribution Patch (149 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-43854
vulnetix vdb fixes CVE-2024-43854
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-43854/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart