CVE-2024-43854 json
block: initialize integrity buffer to zero before writing it to media
published 2024-08-17 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-40504
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
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.
Patch / fix
- Linux Linux 4.19.322, 5.4.284, 5.10.226, 5.15.165, 6.1.103, 6.6.44, 6.10.3, 6.11
- linux Debian 12 6.1.106-1
- linux Debian 14, Debian 13 6.10.3-1
debian advisories DEBIAN-CVE-2024-43854
- linux Ubuntu 20.04 LTS 5.4.0-200.220
- linux Ubuntu 22.04 LTS 5.15.0-125.135
- linux Ubuntu 24.04 LTS 6.8.0-50.51
- linux-aws Ubuntu 20.04 LTS 5.4.0-1135.145
- linux-aws Ubuntu 22.04 LTS 5.15.0-1072.78
- linux-aws Ubuntu 24.04 LTS 6.8.0-1020.22
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1139.148
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1071.79
ubuntu advisories UBUNTU-CVE-2024-43854
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-503.16.1.el9_5
- rv RHEL 9 5.14.0-503.16.1.el9_5
- perf RHEL 9 5.14.0-503.16.1.el9_5
- rtla RHEL 9 5.14.0-503.16.1.el9_5
- bpftool RHEL 9 7.4.0-503.16.1.el9_5
- libperf RHEL 9 5.14.0-503.16.1.el9_5
- kernel-rt RHEL 9 5.14.0-503.16.1.el9_5
- kernel-64k RHEL 9 5.14.0-503.16.1.el9_5
red hat advisories RHSA-2024:10939RHSA-2024:10773RHSA-2024:10772RHSA-2024:8870RHSA-2024:8856RHSA-2024:8617
- kernel-rt Linux Micro 6.0 6.4.0-10.1
- kernel-source-rt Linux Micro 6.0 6.4.0-10.1
- kernel-livepatch-MICRO-6-0-RT_Update_2 Linux Micro 6.0 1-1.1
- kernel-source Linux Micro 6.0 6.4.0-19.1
- kernel-default Linux Micro 6.0 6.4.0-19.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-19.1
- kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
- kernel-livepatch-MICRO-6-0_Update_2 Linux Micro 6.0 1-1.1
suse advisories SUSE-SU-2025:20047-1SUSE-SU-2025:20044-1SUSE-SU-2024:4345-1SUSE-SU-2024:4131-1SUSE-SU-2024:3483-1SUSE-SU-2024:3383-1
- kernel AlmaLinux 9 5.14.0-503.16.1.el9_5
- rv AlmaLinux 9 5.14.0-503.16.1.el9_5
- perf AlmaLinux 9 5.14.0-503.16.1.el9_5
- rtla AlmaLinux 9 5.14.0-503.16.1.el9_5
- bpftool AlmaLinux 9 7.4.0-503.16.1.el9_5
- libperf AlmaLinux 9 5.14.0-503.16.1.el9_5
- kernel-rt AlmaLinux 9 5.14.0-503.16.1.el9_5
- kernel-64k AlmaLinux 9 5.14.0-503.16.1.el9_5
almalinux advisories ALSA-2024:10939ALSA-2024:8856ALSA-2024:8870ALSA-2024:8617
- kernel Rocky Linux 9 5.14.0-427.42.1.el9_4
- kernel-rt Rocky Linux 8 4.18.0-553.27.1.rt7.368.el8_10
- kernel Rocky Linux 8 4.18.0-553.27.1.el8_10
rocky linux advisories RLSA-2024:8617RLSA-2024:8870RLSA-2024:8856
- kernel CBL-Mariner 2.0 5.15.167.1-1
- kernel Azure Linux 3.0 6.6.47.1-1
azure linux advisories AZL-47958AZL-48033
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/9f4af4cf08f9a0329ade3d938f55d2220c40d0a6 commit
- git.kernel.org/stable/c/129f95948a96105c1fad8e612c9097763e88ac5f commit
- git.kernel.org/stable/c/3fd11fe4f20756b4c0847f755a64cd96f8c6a005 commit
- git.kernel.org/stable/c/cf6b45ea7a8df0f61bded1dc4a8561ac6ad143d2 commit
- git.kernel.org/stable/c/d418313bd8f55c079a7da12651951b489a638ac1 commit
- git.kernel.org/stable/c/23a19655fb56f241e592041156dfb1c6d04da644 commit
- git.kernel.org/stable/c/ebc0e91ba76dc6544fff9f5b66408b1982806a00 commit
- git.kernel.org/stable/c/899ee2c3829c5ac14bfc7d3c4a5846c0b709b78f commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-43854 updated cvss 5.5
kernel: block: initialize integrity buffer to zero before writing it to media
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: workaround, no fix planned “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.”
-
Red Hat CodeReady Linux Builder (v. 9) libperf 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-s390x 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-x86_64 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-aarch64 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-ppc64le 5.14.0-503.16.1.el9_5fixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10939
-
Red Hat CodeReady Linux Builder EUS (v.9.2) kernel-debuginfo-common-s390x 5.14.0-284.95.1.el9_2, kernel-debuginfo-common-x86_64 5.14.0-284.95.1.el9_2, kernel-debuginfo-common-aarch64 5.14.0-284.95.1.el9_2, kernel-debuginfo-common-ppc64le 5.14.0-284.95.1.el9_2fixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10772
-
Red Hat Enterprise Linux AppStream (v. 9) rv 5.14.0-427.42.1.el9_4, rv 5.14.0-503.16.1.el9_5, perf 5.14.0-427.42.1.el9_4, perf 5.14.0-503.16.1.el9_5, rtla 5.14.0-427.42.1.el9_4, rtla 5.14.0-503.16.1.el9_5, +18 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8617
-
Red Hat Enterprise Linux AppStream EUS (v.9.2) perf 5.14.0-284.95.1.el9_2, rtla 5.14.0-284.95.1.el9_2, kernel-devel-matched 5.14.0-284.95.1.el9_2, kernel-64k-devel-matched 5.14.0-284.95.1.el9_2, kernel-debug-devel-matched 5.14.0-284.95.1.el9_2, kernel-debuginfo-common-s390x 5.14.0-284.95.1.el9_2, +5 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10772
-
Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-553.27.1.el8_10, kernel 4.18.0-553.27.1.el8_10, bpftool 4.18.0-553.27.1.el8_10, kernel-core 4.18.0-553.27.1.el8_10, kernel-tools 4.18.0-553.27.1.el8_10, python3-perf 4.18.0-553.27.1.el8_10, +15 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8856
-
Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.3.0-427.42.1.el9_4, bpftool 7.4.0-503.16.1.el9_5, kernel 5.14.0-427.42.1.el9_4, kernel 5.14.0-503.16.1.el9_5, kernel-64k 5.14.0-427.42.1.el9_4, kernel-64k 5.14.0-503.16.1.el9_5, +63 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8617
-
Red Hat Enterprise Linux BaseOS EUS (v.9.2) bpftool 7.0.0-284.95.1.el9_2, kernel 5.14.0-284.95.1.el9_2, kernel-64k 5.14.0-284.95.1.el9_2, kernel-core 5.14.0-284.95.1.el9_2, kernel-tools 5.14.0-284.95.1.el9_2, python3-perf 5.14.0-284.95.1.el9_2, +28 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10772
show 11 moreshow fewer
-
Red Hat Enterprise Linux CRB (v. 8) kernel-debuginfo-common-x86_64 4.18.0-553.27.1.el8_10, kernel-debuginfo-common-aarch64 4.18.0-553.27.1.el8_10, kernel-debuginfo-common-ppc64le 4.18.0-553.27.1.el8_10fixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8856
-
Red Hat Enterprise Linux CRB (v. 9) libperf 5.14.0-427.42.1.el9_4, kernel-debuginfo-common-s390x 5.14.0-427.42.1.el9_4, kernel-debuginfo-common-x86_64 5.14.0-427.42.1.el9_4, kernel-debuginfo-common-aarch64 5.14.0-427.42.1.el9_4, kernel-debuginfo-common-ppc64le 5.14.0-427.42.1.el9_4fixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8617
-
Red Hat Enterprise Linux NFV (v. 8) kernel-rt 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-kvm 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-core 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-modules 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-debug-kvm 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-debug-core 4.18.0-553.27.1.rt7.368.el8_10, +4 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8870
-
Red Hat Enterprise Linux NFV (v. 9) kernel-rt 5.14.0-427.42.1.el9_4, kernel-rt-kvm 5.14.0-427.42.1.el9_4, kernel-rt-core 5.14.0-427.42.1.el9_4, kernel-rt-modules 5.14.0-427.42.1.el9_4, kernel-rt-debug-kvm 5.14.0-427.42.1.el9_4, kernel-rt-debug-core 5.14.0-427.42.1.el9_4, +6 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8617
-
Red Hat Enterprise Linux Real Time (v. 9) kernel-rt 5.14.0-503.16.1.el9_5, kernel-rt-core 5.14.0-503.16.1.el9_5, kernel-rt-modules 5.14.0-503.16.1.el9_5, kernel-rt-debug-core 5.14.0-503.16.1.el9_5, kernel-rt-modules-core 5.14.0-503.16.1.el9_5, kernel-rt-debug-modules 5.14.0-503.16.1.el9_5, +4 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10939
-
Red Hat Enterprise Linux Real Time EUS (v.9.2) kernel-rt 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-core 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-modules 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-debug-core 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-modules-core 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-debug-modules 5.14.0-284.95.1.rt14.380.el9_2, +4 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10773
-
Red Hat Enterprise Linux Real Time for NFV (v. 9) kernel-rt 5.14.0-503.16.1.el9_5, kernel-rt-kvm 5.14.0-503.16.1.el9_5, kernel-rt-core 5.14.0-503.16.1.el9_5, kernel-rt-modules 5.14.0-503.16.1.el9_5, kernel-rt-debug-kvm 5.14.0-503.16.1.el9_5, kernel-rt-debug-core 5.14.0-503.16.1.el9_5, +6 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10939
-
Red Hat Enterprise Linux Real Time for NFV EUS (v.9.2) kernel-rt 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-kvm 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-core 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-modules 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-debug-kvm 5.14.0-284.95.1.rt14.380.el9_2, kernel-rt-debug-core 5.14.0-284.95.1.rt14.380.el9_2, +6 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:10773
-
Red Hat Enterprise Linux RT (v. 8) kernel-rt 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-core 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-modules 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-debug-core 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-debug-modules 4.18.0-553.27.1.rt7.368.el8_10, kernel-rt-modules-extra 4.18.0-553.27.1.rt7.368.el8_10, +2 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8870
-
Red Hat Enterprise Linux RT (v. 9) kernel-rt 5.14.0-427.42.1.el9_4, kernel-rt-core 5.14.0-427.42.1.el9_4, kernel-rt-modules 5.14.0-427.42.1.el9_4, kernel-rt-debug-core 5.14.0-427.42.1.el9_4, kernel-rt-modules-core 5.14.0-427.42.1.el9_4, kernel-rt-debug-modules 5.14.0-427.42.1.el9_4, +4 morefixed: vendor fix “Fix this issue by adding the __GFP_ZERO flag to allocations for writes.” RHSA-2024:8617
-
Red Hat Enterprise Linux AppStream EUS (v.9.2) kernel-doc 5.14.0-284.95.1.el9_2not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
- git.kernel.org /stable/c/9f4af4cf08f9a0329ade3d938f55d2220c40d0a6
- git.kernel.org /stable/c/129f95948a96105c1fad8e612c9097763e88ac5f
- git.kernel.org /stable/c/3fd11fe4f20756b4c0847f755a64cd96f8c6a005
-
git.kernel.org
/stable/c/cf6b45ea7a8df0f61bded1dc4a8561ac6ad143d2
patch
-
git.kernel.org
/stable/c/d418313bd8f55c079a7da12651951b489a638ac1
patch
-
git.kernel.org
/stable/c/23a19655fb56f241e592041156dfb1c6d04da644
patch
-
git.kernel.org
/stable/c/ebc0e91ba76dc6544fff9f5b66408b1982806a00
patch
-
git.kernel.org
/stable/c/899ee2c3829c5ac14bfc7d3c4a5846c0b709b78f
patch
- lists.debian.org /debian-lts-announce/2025/01/msg00001.html
- lists.debian.org /debian-lts-announce/2024/10/msg00003.html
Sources
- CVE List CVE-2024-43854
- NVD CVE-2024-43854
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.