CVE-2024-49912: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Handle null 'stream_status' in 'planes_changed_for_existing_stream' This commit adds a null check for 'stream_status' in the function 'planes_changed_for_existing_stream'. Previously, the code assumed 'stream_status' could be null, but did not handle the case where it was actually null. This could lead to a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:3784 planes_changed_for_existing_stream() error: we previously assumed 'stream_status' could be null (see line 3774)
AI Analysis
Technical Summary
CVE-2024-49912 is a vulnerability identified in the Linux kernel, specifically within the AMD GPU driver component related to the Direct Rendering Manager (DRM) subsystem. The flaw exists in the function 'planes_changed_for_existing_stream' located in the file dc_resource.c, part of the AMD display driver code. The vulnerability arises because the code previously assumed that the pointer 'stream_status' could never be null, but in reality, it can be. This incorrect assumption leads to a null pointer dereference when the function attempts to access or manipulate 'stream_status' without verifying its validity. Null pointer dereferences in kernel space typically cause a kernel panic or system crash, leading to a denial of service (DoS) condition. The issue was detected by static analysis tool smatch and has been addressed by adding a null check for 'stream_status' in the affected function. The vulnerability affects specific Linux kernel versions identified by commit hashes (all the same hash repeated in the data), indicating a particular code state before the patch. There are no known exploits in the wild at the time of publication, and no CVSS score has been assigned yet. The vulnerability is categorized as a software bug that can cause system instability or crash due to improper handling of null pointers in the AMD GPU driver within the Linux kernel.
Potential Impact
For European organizations, the impact of CVE-2024-49912 primarily involves potential system instability or denial of service on Linux systems running vulnerable kernel versions with AMD GPU hardware. This could affect servers, desktops, or workstations that rely on AMD graphics hardware and use the affected Linux kernel versions. The denial of service could disrupt critical services, especially in environments where uptime and availability are crucial, such as financial institutions, healthcare providers, and public sector organizations. While this vulnerability does not appear to allow privilege escalation or remote code execution, the resulting kernel panic could be exploited by an attacker with local access to cause repeated crashes, leading to operational disruption. Organizations using AMD GPUs in their Linux infrastructure should be aware of this risk, particularly if they deploy graphical workloads or GPU-accelerated applications. The lack of known exploits reduces immediate risk, but the vulnerability's presence in the kernel means that any local user or process triggering the flaw could cause a system crash, impacting availability.
Mitigation Recommendations
To mitigate CVE-2024-49912, European organizations should: 1) Apply the official Linux kernel patches that include the null pointer check fix for the AMD GPU driver as soon as they become available from their Linux distribution vendors or upstream kernel sources. 2) Identify and inventory Linux systems running AMD GPU hardware and verify kernel versions to determine exposure. 3) Temporarily restrict untrusted local user access on affected systems to reduce the risk of exploitation via local triggering of the null pointer dereference. 4) Monitor system logs and kernel crash reports for signs of crashes related to the AMD GPU driver to detect potential exploitation attempts or accidental triggers. 5) Consider deploying kernel live patching solutions if available to minimize downtime during patch application. 6) Coordinate with hardware and software vendors to ensure compatibility and stability of updated kernel versions in production environments. 7) For critical systems where GPU functionality is not essential, consider disabling the AMD GPU driver as a temporary workaround until patches are applied.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Poland, Italy, Spain
CVE-2024-49912: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Handle null 'stream_status' in 'planes_changed_for_existing_stream' This commit adds a null check for 'stream_status' in the function 'planes_changed_for_existing_stream'. Previously, the code assumed 'stream_status' could be null, but did not handle the case where it was actually null. This could lead to a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:3784 planes_changed_for_existing_stream() error: we previously assumed 'stream_status' could be null (see line 3774)
AI-Powered Analysis
Technical Analysis
CVE-2024-49912 is a vulnerability identified in the Linux kernel, specifically within the AMD GPU driver component related to the Direct Rendering Manager (DRM) subsystem. The flaw exists in the function 'planes_changed_for_existing_stream' located in the file dc_resource.c, part of the AMD display driver code. The vulnerability arises because the code previously assumed that the pointer 'stream_status' could never be null, but in reality, it can be. This incorrect assumption leads to a null pointer dereference when the function attempts to access or manipulate 'stream_status' without verifying its validity. Null pointer dereferences in kernel space typically cause a kernel panic or system crash, leading to a denial of service (DoS) condition. The issue was detected by static analysis tool smatch and has been addressed by adding a null check for 'stream_status' in the affected function. The vulnerability affects specific Linux kernel versions identified by commit hashes (all the same hash repeated in the data), indicating a particular code state before the patch. There are no known exploits in the wild at the time of publication, and no CVSS score has been assigned yet. The vulnerability is categorized as a software bug that can cause system instability or crash due to improper handling of null pointers in the AMD GPU driver within the Linux kernel.
Potential Impact
For European organizations, the impact of CVE-2024-49912 primarily involves potential system instability or denial of service on Linux systems running vulnerable kernel versions with AMD GPU hardware. This could affect servers, desktops, or workstations that rely on AMD graphics hardware and use the affected Linux kernel versions. The denial of service could disrupt critical services, especially in environments where uptime and availability are crucial, such as financial institutions, healthcare providers, and public sector organizations. While this vulnerability does not appear to allow privilege escalation or remote code execution, the resulting kernel panic could be exploited by an attacker with local access to cause repeated crashes, leading to operational disruption. Organizations using AMD GPUs in their Linux infrastructure should be aware of this risk, particularly if they deploy graphical workloads or GPU-accelerated applications. The lack of known exploits reduces immediate risk, but the vulnerability's presence in the kernel means that any local user or process triggering the flaw could cause a system crash, impacting availability.
Mitigation Recommendations
To mitigate CVE-2024-49912, European organizations should: 1) Apply the official Linux kernel patches that include the null pointer check fix for the AMD GPU driver as soon as they become available from their Linux distribution vendors or upstream kernel sources. 2) Identify and inventory Linux systems running AMD GPU hardware and verify kernel versions to determine exposure. 3) Temporarily restrict untrusted local user access on affected systems to reduce the risk of exploitation via local triggering of the null pointer dereference. 4) Monitor system logs and kernel crash reports for signs of crashes related to the AMD GPU driver to detect potential exploitation attempts or accidental triggers. 5) Consider deploying kernel live patching solutions if available to minimize downtime during patch application. 6) Coordinate with hardware and software vendors to ensure compatibility and stability of updated kernel versions in production environments. 7) For critical systems where GPU functionality is not essential, consider disabling the AMD GPU driver as a temporary workaround until patches are applied.
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-21T12:17:06.028Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9826c4522896dcbe0995
Added to database: 5/21/2025, 9:08:54 AM
Last enriched: 6/28/2025, 9:39:36 PM
Last updated: 11/27/2025, 4:06:11 AM
Views: 28
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-66314: CWE-269 Improper Privilege Management in ZTE ElasticNet UME R32
HighCVE-2025-34351: CWE-1188 Insecure Default Initialization of Resource in The Ray Team Anyscale Ray
CriticalCVE-2025-13762: CWE-20 Improper Input Validation in CyberArk CyberArk Secure Web Sessions Extension
MediumCVE-2025-12713: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wpoets Soundslides
MediumCVE-2025-12712: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in gungorbudak Shouty
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.