Kernel memory disclosure via unchecked SDMA index
Published Jun 25, 2024 · Updated Aug 5, 2026
Out-of-bounds read in Linux kernel AMDGPU SDMA 4.0 code allows local users to read memory outside the SDMA instance array. The sdma_v4_0_process_trap_irq handler uses the result of sdma_v4_0_irq_id_to_seq as an array index without rejecting its -EINVAL return for an unknown interrupt client ID. Triggering the flaw requires local low-privileged access and affected AMDGPU SDMA 4.0 hardware; the resulting read can expose kernel memory or interrupt the system.
Summary
What happened
Out-of-bounds read in Linux kernel AMDGPU SDMA 4.0 code allows local users to read memory outside the SDMA instance array. The sdma_v4_0_process_trap_irq handler uses the result of sdma_v4_0_irq_id_to_seq as an array index without rejecting its -EINVAL return for an unknown interrupt client ID. Triggering the flaw requires local low-privileged access and affected AMDGPU SDMA 4.0 hardware; the resulting read can expose kernel memory or interrupt the system.
The record
- CVE
- CVE-2024-39471
- Published
- Jun 25, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=5.4
- Affected versionversion=7d0e6329dfdcfe48311f8888d6a8dfa73bee00a9 <011552f29f20842c9a7a21bffe1f6a2d6457ba46
- Affected versionversion=7d0e6329dfdcfe48311f8888d6a8dfa73bee00a9 <0964c84b93db7fbf74f357c1e20957850e092db3
- Affected versionversion=7d0e6329dfdcfe48311f8888d6a8dfa73bee00a9 <5594971e02764aa1c8210ffb838cb4e7897716e8
- Affected versionversion=7d0e6329dfdcfe48311f8888d6a8dfa73bee00a9 <5b0a3dc3e87821acb80e841b464d335aff242691
- Affected versionversion=7d0e6329dfdcfe48311f8888d6a8dfa73bee00a9 <8112fa72b7f139052843ff484130d6f97e9f052f
- Affected versionversion=7d0e6329dfdcfe48311f8888d6a8dfa73bee00a9 <8b2faf1a4f3b6c748c0da36cda865a226534d520
- Affected versionversion=7d0e6329dfdcfe48311f8888d6a8dfa73bee00a9 <ea906e9ac61e3152bef63597f2d9f4a812fc346a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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