Kernel warning via oversized AMDGPU DMA segments
Published Dec 27, 2024 · Updated May 11, 2026
Improper DMA segment handling in the Linux kernel's AMDGPU driver allows local users to trigger a kernel warning during GPU memory allocation. The driver leaves the device's maximum scatter-gather segment size at an unsuitable default, so amdgpu_bo_move can map segments longer than the DMA layer permits. Reachability requires an AMD GPU, the AMDGPU/KFD path, and local access capable of issuing a GPU-memory allocation ioctl; the published trace demonstrates a warning rather than a crash or code execution.
Summary
What happened
Improper DMA segment handling in the Linux kernel's AMDGPU driver allows local users to trigger a kernel warning during GPU memory allocation. The driver leaves the device's maximum scatter-gather segment size at an unsuitable default, so amdgpu_bo_move can map segments longer than the DMA layer permits. Reachability requires an AMD GPU, the AMDGPU/KFD path, and local access capable of issuing a GPU-memory allocation ioctl; the published trace demonstrates a warning rather than a crash or code execution.
The record
- CVE
- CVE-2024-56594
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 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=4.2
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <13c3a54f48a612a117dfd82a9dd91732261e869d
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <76581147b05c2adb6b47bbc697521725f10224e4
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <76649ccf97e2cd72b62e34ed2fba6e0f89497eab
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <b5807a08954fdf914ef80b49aaa6cda965ecc95c
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <b9e52a96ec92245bf15dabba1d3d862d7a03efb8
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <e2e97435783979124ba92d6870415c57ecfef6a5
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <ff0346a74627a5f607a33a3852586f8c7f678329
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
No sourced classifications are available.
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