Skip to main content

CVE-2024-46867: Vulnerability in Linux Linux

High
VulnerabilityCVE-2024-46867cvecve-2024-46867
Published: Fri Sep 27 2024 (09/27/2024, 12:42:55 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/client: fix deadlock in show_meminfo() There is a real deadlock as well as sleeping in atomic() bug in here, if the bo put happens to be the last ref, since bo destruction wants to grab the same spinlock and sleeping locks. Fix that by dropping the ref using xe_bo_put_deferred(), and moving the final commit outside of the lock. Dropping the lock around the put is tricky since the bo can go out of scope and delete itself from the list, making it difficult to navigate to the next list entry. (cherry picked from commit 0083b8e6f11d7662283a267d4ce7c966812ffd8a)

AI-Powered Analysis

AILast updated: 06/28/2025, 18:57:37 UTC

Technical Analysis

CVE-2024-46867 is a vulnerability identified in the Linux kernel, specifically within the Direct Rendering Manager (DRM) subsystem's Xe client driver. The issue arises in the show_meminfo() function, where a deadlock condition and improper sleeping in atomic context occur. The root cause is related to the handling of buffer objects (bo) references during their destruction. When the last reference to a buffer object is released, the destruction process attempts to acquire a spinlock that is already held, causing a deadlock. Additionally, the code incorrectly performs sleeping operations while holding atomic locks, which is unsafe and can lead to kernel instability. The fix involves deferring the release of the buffer object reference using xe_bo_put_deferred() and moving the final commit operation outside the locked section. This approach avoids the deadlock by ensuring that the buffer object can safely delete itself from the list without holding the spinlock, which is complex due to the risk of the object going out of scope. This vulnerability is significant because it affects the Linux kernel's graphics subsystem, which is widely used across many Linux distributions and environments. Although no known exploits are reported in the wild, the presence of a deadlock and improper locking can lead to system hangs or crashes, impacting system availability. The vulnerability was published on September 27, 2024, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions with the DRM Xe client driver enabled, which includes many desktop, server, and embedded systems using Intel graphics hardware. The deadlock can cause system hangs or kernel panics, leading to denial of service conditions. This can disrupt critical services, especially in sectors relying on Linux-based infrastructure such as finance, telecommunications, government, and manufacturing. Systems used in cloud environments or data centers that utilize Linux with Intel graphics acceleration could also be impacted, potentially affecting virtualized workloads and containerized applications. Although the vulnerability does not appear to allow privilege escalation or data leakage directly, the availability impact can be severe in environments requiring high uptime and reliability. Given the widespread use of Linux in European IT infrastructure, the vulnerability could affect a broad range of organizations if unpatched kernels are deployed.

Mitigation Recommendations

European organizations should prioritize updating their Linux kernel to the patched versions that include the fix for CVE-2024-46867. Since the vulnerability involves kernel-level deadlocks, applying vendor or distribution-provided kernel updates is the most effective mitigation. Organizations should: 1) Identify all systems running affected Linux kernel versions with Intel DRM Xe client drivers. 2) Test and deploy kernel updates from trusted sources promptly. 3) For environments where immediate patching is not feasible, consider temporarily disabling or limiting use of the affected graphics driver if possible, to reduce exposure. 4) Monitor system logs for signs of deadlocks or kernel panics related to graphics operations. 5) Implement robust backup and recovery procedures to minimize downtime in case of system crashes. 6) Engage with Linux distribution vendors for guidance on backported patches and security advisories. 7) For cloud or virtualized environments, coordinate with cloud providers to ensure underlying host kernels are patched. These steps go beyond generic advice by focusing on driver-specific mitigation and operational monitoring tailored to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-09-11T15:12:18.294Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9825c4522896dcbe03a3

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

Last enriched: 6/28/2025, 6:57:37 PM

Last updated: 8/16/2025, 3:42:47 AM

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