CVE-2024-50149: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Don't free job in TDR Freeing job in TDR is not safe as TDR can pass the run_job thread resulting in UAF. It is only safe for free job to naturally be called by the scheduler. Rather free job in TDR, add to pending list. (cherry picked from commit ea2f6a77d0c40d97f4a4dc93fee4afe15d94926d)
AI Analysis
Technical Summary
CVE-2024-50149 is a high-severity use-after-free (UAF) vulnerability identified in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically within the Intel Xe graphics driver (xe). The flaw arises from improper handling of job freeing during a Timeout Detection and Recovery (TDR) event. In normal operation, job objects are freed by the scheduler, which ensures safe memory management. However, the vulnerable code attempts to free a job directly within the TDR handler, which can lead to a use-after-free condition because the TDR may pass the run_job thread that still references the job object. This unsafe freeing can cause memory corruption, potentially allowing an attacker to execute arbitrary code with kernel privileges or cause a denial of service by crashing the system. The vulnerability is tracked under CWE-416 (Use After Free) and has been assigned a CVSS v3.1 score of 7.8, indicating high severity. Exploitation requires local access with low privileges (PR:L), no user interaction (UI:N), and the attack vector is local (AV:L). The vulnerability affects specific Linux kernel versions identified by commit hashes e275d61c5f3ffc250b2a9601d36fbd11b4db774b. The fix involves modifying the TDR handler to avoid freeing the job directly and instead adding it to a pending list to be freed safely by the scheduler, preventing the unsafe memory access. No known exploits are currently reported in the wild, but the potential impact on confidentiality, integrity, and availability is significant due to kernel-level code execution risks.
Potential Impact
For European organizations, this vulnerability poses a serious risk, especially for those relying on Linux systems with Intel Xe graphics hardware, such as servers, workstations, or embedded devices running vulnerable kernel versions. Successful exploitation could allow attackers with local access to escalate privileges to kernel level, leading to full system compromise, data theft, or disruption of critical services. This is particularly concerning for sectors with high reliance on Linux infrastructure, including finance, telecommunications, government, and critical infrastructure operators. The vulnerability could be leveraged in multi-user environments or through compromised accounts to pivot and escalate privileges. Additionally, the potential for denial of service could impact availability of essential services. Given the local attack vector, insider threats or attackers who have gained initial footholds could exploit this flaw to deepen their access. The lack of required user interaction facilitates automated exploitation in compromised environments. Consequently, organizations must prioritize patching to maintain system integrity and availability.
Mitigation Recommendations
Organizations should immediately identify Linux systems running affected kernel versions with Intel Xe graphics drivers and apply the official patches or kernel updates that address CVE-2024-50149. Since the vulnerability involves kernel-level code, updating the kernel to a fixed version is the most effective mitigation. In environments where immediate patching is not feasible, restricting local access to trusted users and enforcing strict privilege separation can reduce exploitation risk. Employing kernel security modules such as SELinux or AppArmor with strict policies may help limit the impact of exploitation. Monitoring system logs for unusual behavior related to the DRM subsystem and run_job threads can provide early detection of exploitation attempts. Additionally, organizations should review and tighten user account controls and audit local access, especially on multi-user systems. For critical infrastructure, consider deploying host-based intrusion detection systems (HIDS) that can detect anomalous kernel activity. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2024-50149: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Don't free job in TDR Freeing job in TDR is not safe as TDR can pass the run_job thread resulting in UAF. It is only safe for free job to naturally be called by the scheduler. Rather free job in TDR, add to pending list. (cherry picked from commit ea2f6a77d0c40d97f4a4dc93fee4afe15d94926d)
AI-Powered Analysis
Technical Analysis
CVE-2024-50149 is a high-severity use-after-free (UAF) vulnerability identified in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically within the Intel Xe graphics driver (xe). The flaw arises from improper handling of job freeing during a Timeout Detection and Recovery (TDR) event. In normal operation, job objects are freed by the scheduler, which ensures safe memory management. However, the vulnerable code attempts to free a job directly within the TDR handler, which can lead to a use-after-free condition because the TDR may pass the run_job thread that still references the job object. This unsafe freeing can cause memory corruption, potentially allowing an attacker to execute arbitrary code with kernel privileges or cause a denial of service by crashing the system. The vulnerability is tracked under CWE-416 (Use After Free) and has been assigned a CVSS v3.1 score of 7.8, indicating high severity. Exploitation requires local access with low privileges (PR:L), no user interaction (UI:N), and the attack vector is local (AV:L). The vulnerability affects specific Linux kernel versions identified by commit hashes e275d61c5f3ffc250b2a9601d36fbd11b4db774b. The fix involves modifying the TDR handler to avoid freeing the job directly and instead adding it to a pending list to be freed safely by the scheduler, preventing the unsafe memory access. No known exploits are currently reported in the wild, but the potential impact on confidentiality, integrity, and availability is significant due to kernel-level code execution risks.
Potential Impact
For European organizations, this vulnerability poses a serious risk, especially for those relying on Linux systems with Intel Xe graphics hardware, such as servers, workstations, or embedded devices running vulnerable kernel versions. Successful exploitation could allow attackers with local access to escalate privileges to kernel level, leading to full system compromise, data theft, or disruption of critical services. This is particularly concerning for sectors with high reliance on Linux infrastructure, including finance, telecommunications, government, and critical infrastructure operators. The vulnerability could be leveraged in multi-user environments or through compromised accounts to pivot and escalate privileges. Additionally, the potential for denial of service could impact availability of essential services. Given the local attack vector, insider threats or attackers who have gained initial footholds could exploit this flaw to deepen their access. The lack of required user interaction facilitates automated exploitation in compromised environments. Consequently, organizations must prioritize patching to maintain system integrity and availability.
Mitigation Recommendations
Organizations should immediately identify Linux systems running affected kernel versions with Intel Xe graphics drivers and apply the official patches or kernel updates that address CVE-2024-50149. Since the vulnerability involves kernel-level code, updating the kernel to a fixed version is the most effective mitigation. In environments where immediate patching is not feasible, restricting local access to trusted users and enforcing strict privilege separation can reduce exploitation risk. Employing kernel security modules such as SELinux or AppArmor with strict policies may help limit the impact of exploitation. Monitoring system logs for unusual behavior related to the DRM subsystem and run_job threads can provide early detection of exploitation attempts. Additionally, organizations should review and tighten user account controls and audit local access, especially on multi-user systems. For critical infrastructure, consider deploying host-based intrusion detection systems (HIDS) that can detect anomalous kernel activity. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-10-21T19:36:19.959Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9825c4522896dcbe00d4
Added to database: 5/21/2025, 9:08:53 AM
Last enriched: 7/3/2025, 12:10:24 AM
Last updated: 8/16/2025, 10:41:28 AM
Views: 18
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.