Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-43854block: initialize integrity buffer to zero before writing it to media

Description

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

  1. ID reserved

    By Linux

  2. Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-43854, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < 9f4af4cf08f9a0329ade3d938f55d2220c40d0a6
    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < 129f95948a96105c1fad8e612c9097763e88ac5f
    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < 3fd11fe4f20756b4c0847f755a64cd96f8c6a005
    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < cf6b45ea7a8df0f61bded1dc4a8561ac6ad143d2
    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < d418313bd8f55c079a7da12651951b489a638ac1
    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < 23a19655fb56f241e592041156dfb1c6d04da644
    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < ebc0e91ba76dc6544fff9f5b66408b1982806a00
    • affected 7ba1ba12eeef0aa7113beb16410ef8b7c748e18b – < 899ee2c3829c5ac14bfc7d3c4a5846c0b709b78f
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 4.19.322 – ≤ 4.19.*
    • unaffected 5.4.284 – ≤ 5.4.*
    • unaffected 5.10.226 – ≤ 5.10.*
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.103 – ≤ 6.1.*
    • unaffected 6.6.44 – ≤ 6.6.*
    • unaffected 6.10.3 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-43854 badge
[![CVE-2024-43854](https://cveledger.app/badge/CVE-2024-43854.svg)](https://cveledger.app/cve/CVE-2024-43854)

Record last updated .