Local service interruption via GFX9 memory leak
Published Dec 29, 2024 · Updated May 11, 2026
Memory leak in the AMD GFX9 graphics driver in Linux 6.12 allows local users to interrupt service during driver reinitialization. The gfx_v9_0_sw_fini function omits amdgpu_gfx_cleaner_shader_sw_fini(adev), leaving cleaner-shader allocations unreleased and GPU state uncleared. Exploitation requires low-privileged local access and GFX9 hardware, and the documented consequence is limited to availability.
Summary
What happened
Memory leak in the AMD GFX9 graphics driver in Linux 6.12 allows local users to interrupt service during driver reinitialization. The gfx_v9_0_sw_fini function omits amdgpu_gfx_cleaner_shader_sw_fini(adev), leaving cleaner-shader allocations unreleased and GPU state uncleared. Exploitation requires low-privileged local access and GFX9 hardware, and the documented consequence is limited to availability.
The record
- CVE
- CVE-2024-56753
- Published
- Dec 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 29, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.12
- Affected versionversion=c2e70d307f4491ff970208a41cce84c95771f340 <720c0376b3d29cbab921a60062fda5980742ed9d
- Affected versionversion=c2e70d307f4491ff970208a41cce84c95771f340 <e47cb9d2533200d49dd5364d4a148119492f8a3d
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo