Skip to main content

CVE-2024-36910: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2024-36910cvecve-2024-36910
Published: Thu May 30 2024 (05/30/2024, 15:29:08 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Don't free decrypted memory In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. The VMBus device UIO driver could free decrypted/shared pages if set_memory_decrypted() fails. Check the decrypted field in the gpadl to decide whether to free the memory.

AI-Powered Analysis

AILast updated: 06/29/2025, 10:09:52 UTC

Technical Analysis

CVE-2024-36910 is a medium-severity vulnerability in the Linux kernel affecting the uio_hv_generic driver, which is part of the Virtual Machine Bus (VMBus) device UIO driver stack used primarily in Hyper-V environments. The vulnerability arises from improper handling of memory encryption state transitions in CoCo (Confidential Computing) virtual machines. Specifically, when the untrusted host causes the set_memory_encrypted() or set_memory_decrypted() kernel functions to fail, the driver may incorrectly free decrypted or shared memory pages without verifying their encryption state. This occurs because the driver does not adequately check the 'decrypted' field in the GPADL (Guest Physical Address Descriptor List) before freeing memory. As a result, decrypted memory that should remain protected could be inadvertently returned to the page allocator as shared memory, potentially leading to functional issues or security risks such as information leakage or memory corruption. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and has a CVSS v3.1 score of 6.2, indicating a medium severity level. Exploitation requires local access (attack vector: local), low attack complexity, no privileges required, and no user interaction. The impact is primarily on availability due to possible memory corruption or system instability, with no direct confidentiality or integrity impact reported. No known exploits are currently in the wild, and patches have been released to address the issue by ensuring proper error handling and validation of memory encryption state before freeing memory pages.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to environments running Linux kernels with Hyper-V virtualization, especially those leveraging confidential computing features. Organizations using CoCo VMs on Hyper-V hosts may experience system instability or crashes if the vulnerability is exploited, potentially disrupting critical services. While the vulnerability does not directly compromise confidentiality or integrity, the improper memory handling could lead to denial-of-service conditions or indirect exposure of sensitive data through memory mismanagement. This is particularly relevant for cloud service providers, data centers, and enterprises relying on Linux-based virtualized infrastructure within Europe. Given the increasing adoption of confidential computing for enhanced data protection, failure to patch this vulnerability could undermine trust in secure VM deployments. However, the requirement for local access and the absence of known exploits reduce the immediate threat level, allowing organizations some time to apply mitigations.

Mitigation Recommendations

European organizations should prioritize updating their Linux kernel to the latest patched versions that address CVE-2024-36910. Specifically, they should ensure that all Hyper-V host and guest systems running CoCo VMs are upgraded to kernels incorporating the fix that properly checks the 'decrypted' field before freeing memory. Additionally, organizations should audit their virtualization environments to identify any use of confidential computing features and restrict local access to trusted users only, minimizing the risk of local exploitation. Implementing strict access controls and monitoring for unusual memory-related errors or system crashes can help detect potential exploitation attempts. For environments where immediate patching is not feasible, disabling confidential computing features or avoiding the use of the vulnerable uio_hv_generic driver may serve as temporary mitigations. Finally, maintaining up-to-date security monitoring and incident response plans tailored to virtualization infrastructure will enhance resilience against exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-05-30T15:25:07.067Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d9828c4522896dcbe264a

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

Last enriched: 6/29/2025, 10:09:52 AM

Last updated: 7/29/2025, 1:09:13 PM

Views: 10

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