Skip to main content

CVE-2024-49858: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2024-49858cvecve-2024-49858
Published: Mon Oct 21 2024 (10/21/2024, 12:27:17 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

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.

AI-Powered Analysis

AILast updated: 06/28/2025, 20:42:06 UTC

Technical Analysis

CVE-2024-49858 is a vulnerability identified in the Linux kernel related to the handling of the TPM (Trusted Platform Module) event log memory region during system boot and kexec operations. Specifically, the issue arises from the use of the EFI_LOADER_DATA memory type for the TPM event log in the EFI configuration table. This memory type is not marked as reserved in the E820 memory map, which is passed to the kernel during a kexec (a mechanism to boot into a new kernel without going through firmware). Because the kernel is unaware that this memory region should be reserved, it can lead to memory corruption when the TPM event log is accessed or parsed. The TPM event log is a Linux-specific construct that caches data from the GetEventLog() boot service. Although the utility of the TPM2 event log after a kexec is limited, corrupted event log data can cause the kernel parsing code to malfunction, potentially resulting in a kernel crash. The fix involves changing the memory type from EFI_LOADER_DATA to EFI_ACPI_RECLAIM_MEMORY, which is always treated as reserved by the E820 conversion logic, thus preventing the kernel from mistakenly accessing or corrupting this memory region. This vulnerability is relevant to Linux kernel versions identified by the commit hash 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and was published on October 21, 2024. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, the impact of CVE-2024-49858 primarily concerns system stability and availability. Linux is widely used across Europe in enterprise servers, cloud infrastructure, and embedded systems, including critical sectors such as finance, telecommunications, government, and manufacturing. A kernel crash caused by this vulnerability could lead to unexpected downtime, data loss, or service interruptions. While this vulnerability does not directly expose confidentiality or integrity of data, the denial of service resulting from kernel crashes can disrupt business operations and impact service-level agreements. Organizations utilizing kexec for kernel updates or specialized boot scenarios are particularly at risk. Additionally, environments leveraging TPM for secure boot or attestation might experience degraded reliability. Since no known exploits exist yet, the immediate risk is low, but the potential for future exploitation to cause denial of service warrants attention, especially in high-availability or security-sensitive deployments.

Mitigation Recommendations

To mitigate CVE-2024-49858, European organizations should: 1) Apply the latest Linux kernel patches that address this vulnerability as soon as they become available from trusted Linux distributions or kernel maintainers. 2) Review and test kexec usage in their environments to ensure that TPM event log handling does not lead to instability. 3) Monitor kernel logs and system stability closely after applying updates or performing kexec operations to detect any anomalies related to TPM event log parsing. 4) For critical systems, consider implementing kernel crash recovery mechanisms and redundant failover to minimize downtime in case of crashes. 5) Engage with Linux distribution vendors to confirm that their kernel packages include the fix. 6) Avoid custom modifications to EFI memory handling unless thoroughly tested against this issue. 7) Maintain up-to-date backups and disaster recovery plans to mitigate the impact of potential kernel crashes. These steps go beyond generic advice by focusing on the specific interaction between EFI memory types, TPM event logs, and kexec usage.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-10-21T12:17:06.016Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9825c4522896dcbe07ab

Added to database: 5/21/2025, 9:08:53 AM

Last enriched: 6/28/2025, 8:42:06 PM

Last updated: 8/15/2025, 5:20:13 PM

Views: 15

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats