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-49858efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption

Description

In the Linux kernel, the following vulnerability has been resolved: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table. The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved. Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let's use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 19 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-49858, 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.21% · top 88% of all CVEs (13 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 33b6d03469b2206fb51ecc37f40411a857ad8fff – < f76b69ab9cf04358266e3cea5748c0c2791fbb08
    • affected 33b6d03469b2206fb51ecc37f40411a857ad8fff – < 11690d7e76842f29b60fbb5b35bc97d206ea0e83
    • affected 33b6d03469b2206fb51ecc37f40411a857ad8fff – < 5b22c038fb2757c652642933de5664da471f8cb7
    • affected 33b6d03469b2206fb51ecc37f40411a857ad8fff – < 19fd2f2c5fb36b61506d3208474bfd8fdf1cada3
    • affected 33b6d03469b2206fb51ecc37f40411a857ad8fff – < 38d9b07d99b789efb6d8dda21f1aaad636c38993
    • affected 33b6d03469b2206fb51ecc37f40411a857ad8fff – < 2e6871a632a99d9b9e2ce3a7847acabe99e5a26e
    • affected 33b6d03469b2206fb51ecc37f40411a857ad8fff – < 77d48d39e99170b528e4f2e9fc5d1d64cdedd386
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.54 – ≤ 6.6.*
    • unaffected 6.10.13 – ≤ 6.10.*
    • unaffected 6.11.2 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .