CVE-2024-26833: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak in dm_sw_fini() After destroying dmub_srv, the memory associated with it is not freed, causing a memory leak: unreferenced object 0xffff896302b45800 (size 1024): comm "(udev-worker)", pid 222, jiffies 4294894636 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 6265fd77): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x340 [<ffffffffc0ea4a94>] dm_dmub_sw_init+0xb4/0x450 [amdgpu] [<ffffffffc0ea4e55>] dm_sw_init+0x15/0x2b0 [amdgpu] [<ffffffffc0ba8557>] amdgpu_device_init+0x1417/0x24e0 [amdgpu] [<ffffffffc0bab285>] amdgpu_driver_load_kms+0x15/0x190 [amdgpu] [<ffffffffc0ba09c7>] amdgpu_pci_probe+0x187/0x4e0 [amdgpu] [<ffffffff9968fd1e>] local_pci_probe+0x3e/0x90 [<ffffffff996918a3>] pci_device_probe+0xc3/0x230 [<ffffffff99805872>] really_probe+0xe2/0x480 [<ffffffff99805c98>] __driver_probe_device+0x78/0x160 [<ffffffff99805daf>] driver_probe_device+0x1f/0x90 [<ffffffff9980601e>] __driver_attach+0xce/0x1c0 [<ffffffff99803170>] bus_for_each_dev+0x70/0xc0 [<ffffffff99804822>] bus_add_driver+0x112/0x210 [<ffffffff99807245>] driver_register+0x55/0x100 [<ffffffff990012d1>] do_one_initcall+0x41/0x300 Fix this by freeing dmub_srv after destroying it.
AI Analysis
Technical Summary
CVE-2024-26833 is a vulnerability identified in the Linux kernel specifically within the AMD GPU driver component (amdgpu), related to the Direct Rendering Manager (DRM) subsystem. The flaw involves a memory leak in the function dm_sw_fini(), which is responsible for cleaning up resources associated with the dmub_srv object. After the dmub_srv service is destroyed, the memory allocated to it is not properly freed, resulting in a persistent memory leak. The vulnerability is rooted in the failure to release a 1024-byte memory allocation, as evidenced by kernel debugging information showing an unreferenced object linked to the udev-worker process. The backtrace indicates the leak occurs during the initialization and destruction phases of the AMD GPU driver, particularly in the dm_dmub_sw_init and dm_sw_init functions. This memory leak can lead to gradual exhaustion of kernel memory resources, potentially degrading system performance or causing instability over time. While the vulnerability does not directly enable code execution or privilege escalation, the leak could be exploited in scenarios where an attacker can repeatedly trigger the driver initialization and teardown, thereby causing denial of service (DoS) conditions due to resource depletion. The issue affects Linux kernel versions containing the specified commit hashes, and it has been resolved by ensuring that the dmub_srv memory is freed after destruction. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-26833 primarily concerns systems running Linux with AMD GPU hardware utilizing the affected amdgpu driver versions. This includes servers, workstations, and potentially embedded systems that rely on Linux for graphics processing. The memory leak could lead to degraded system performance or crashes if the leak accumulates over time, especially in environments with frequent GPU driver reloads or dynamic GPU resource management. Critical infrastructure or data centers using AMD GPUs for compute or graphical workloads may experience reduced availability or require more frequent reboots or maintenance, impacting operational continuity. Although the vulnerability does not directly compromise confidentiality or integrity, the availability impact could disrupt business processes, particularly in sectors like finance, manufacturing, or research where Linux-based AMD GPU systems are prevalent. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed promptly to prevent potential DoS attacks or system instability.
Mitigation Recommendations
European organizations should apply the Linux kernel patches that address this memory leak as soon as they become available from trusted sources or Linux distribution vendors. Specifically, updating to kernel versions that include the fix for CVE-2024-26833 will ensure the dmub_srv memory is properly freed. Organizations should audit their systems to identify those running affected kernel versions with AMD GPU drivers and prioritize patching accordingly. In environments where immediate patching is not feasible, monitoring system memory usage related to GPU driver processes can help detect abnormal leaks early. Additionally, limiting unprivileged user access to trigger GPU driver reloads or udev-worker processes can reduce exploitation risk. For critical systems, consider implementing kernel memory leak detection tools and automated alerts to catch similar issues proactively. Coordination with hardware vendors and Linux distribution maintainers is recommended to ensure timely updates and support.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Poland, Italy, Spain
CVE-2024-26833: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak in dm_sw_fini() After destroying dmub_srv, the memory associated with it is not freed, causing a memory leak: unreferenced object 0xffff896302b45800 (size 1024): comm "(udev-worker)", pid 222, jiffies 4294894636 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 6265fd77): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x340 [<ffffffffc0ea4a94>] dm_dmub_sw_init+0xb4/0x450 [amdgpu] [<ffffffffc0ea4e55>] dm_sw_init+0x15/0x2b0 [amdgpu] [<ffffffffc0ba8557>] amdgpu_device_init+0x1417/0x24e0 [amdgpu] [<ffffffffc0bab285>] amdgpu_driver_load_kms+0x15/0x190 [amdgpu] [<ffffffffc0ba09c7>] amdgpu_pci_probe+0x187/0x4e0 [amdgpu] [<ffffffff9968fd1e>] local_pci_probe+0x3e/0x90 [<ffffffff996918a3>] pci_device_probe+0xc3/0x230 [<ffffffff99805872>] really_probe+0xe2/0x480 [<ffffffff99805c98>] __driver_probe_device+0x78/0x160 [<ffffffff99805daf>] driver_probe_device+0x1f/0x90 [<ffffffff9980601e>] __driver_attach+0xce/0x1c0 [<ffffffff99803170>] bus_for_each_dev+0x70/0xc0 [<ffffffff99804822>] bus_add_driver+0x112/0x210 [<ffffffff99807245>] driver_register+0x55/0x100 [<ffffffff990012d1>] do_one_initcall+0x41/0x300 Fix this by freeing dmub_srv after destroying it.
AI-Powered Analysis
Technical Analysis
CVE-2024-26833 is a vulnerability identified in the Linux kernel specifically within the AMD GPU driver component (amdgpu), related to the Direct Rendering Manager (DRM) subsystem. The flaw involves a memory leak in the function dm_sw_fini(), which is responsible for cleaning up resources associated with the dmub_srv object. After the dmub_srv service is destroyed, the memory allocated to it is not properly freed, resulting in a persistent memory leak. The vulnerability is rooted in the failure to release a 1024-byte memory allocation, as evidenced by kernel debugging information showing an unreferenced object linked to the udev-worker process. The backtrace indicates the leak occurs during the initialization and destruction phases of the AMD GPU driver, particularly in the dm_dmub_sw_init and dm_sw_init functions. This memory leak can lead to gradual exhaustion of kernel memory resources, potentially degrading system performance or causing instability over time. While the vulnerability does not directly enable code execution or privilege escalation, the leak could be exploited in scenarios where an attacker can repeatedly trigger the driver initialization and teardown, thereby causing denial of service (DoS) conditions due to resource depletion. The issue affects Linux kernel versions containing the specified commit hashes, and it has been resolved by ensuring that the dmub_srv memory is freed after destruction. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-26833 primarily concerns systems running Linux with AMD GPU hardware utilizing the affected amdgpu driver versions. This includes servers, workstations, and potentially embedded systems that rely on Linux for graphics processing. The memory leak could lead to degraded system performance or crashes if the leak accumulates over time, especially in environments with frequent GPU driver reloads or dynamic GPU resource management. Critical infrastructure or data centers using AMD GPUs for compute or graphical workloads may experience reduced availability or require more frequent reboots or maintenance, impacting operational continuity. Although the vulnerability does not directly compromise confidentiality or integrity, the availability impact could disrupt business processes, particularly in sectors like finance, manufacturing, or research where Linux-based AMD GPU systems are prevalent. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed promptly to prevent potential DoS attacks or system instability.
Mitigation Recommendations
European organizations should apply the Linux kernel patches that address this memory leak as soon as they become available from trusted sources or Linux distribution vendors. Specifically, updating to kernel versions that include the fix for CVE-2024-26833 will ensure the dmub_srv memory is properly freed. Organizations should audit their systems to identify those running affected kernel versions with AMD GPU drivers and prioritize patching accordingly. In environments where immediate patching is not feasible, monitoring system memory usage related to GPU driver processes can help detect abnormal leaks early. Additionally, limiting unprivileged user access to trigger GPU driver reloads or udev-worker processes can reduce exploitation risk. For critical systems, consider implementing kernel memory leak detection tools and automated alerts to catch similar issues proactively. Coordination with hardware vendors and Linux distribution maintainers is recommended to ensure timely updates and support.
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-02-19T14:20:24.181Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982bc4522896dcbe3d0d
Added to database: 5/21/2025, 9:08:59 AM
Last enriched: 6/29/2025, 7:10:40 PM
Last updated: 8/14/2025, 5:22:34 PM
Views: 12
Related Threats
CVE-2025-8878: CWE-94 Improper Control of Generation of Code ('Code Injection') in properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress
MediumCVE-2025-8143: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in pencidesign Soledad
MediumCVE-2025-8142: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in pencidesign Soledad
HighCVE-2025-8105: CWE-94 Improper Control of Generation of Code ('Code Injection') in pencidesign Soledad
HighCVE-2025-8719: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in reubenthiessen Translate This gTranslate Shortcode
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.