System crash via unchecked GPU voltage index
Published Jul 12, 2024 · Updated May 11, 2026
An out-of-bounds write in the Linux kernel amdgpu driver allows local users to crash affected systems through invalid voltage indices. The sumo_construct_vid_mapping_table function uses usVoltageIndex to select a vid_mapping_table entry without first ensuring that the index is below SUMO_MAX_NUMBER_VOLTAGES. The legacy AMD GPU power-management path and low-privileged local access are required, and the published consequence is a system crash without data disclosure or modification.
Summary
What happened
An out-of-bounds write in the Linux kernel amdgpu driver allows local users to crash affected systems through invalid voltage indices. The sumo_construct_vid_mapping_table function uses usVoltageIndex to select a vid_mapping_table entry without first ensuring that the index is below SUMO_MAX_NUMBER_VOLTAGES. The legacy AMD GPU power-management path and low-privileged local access are required, and the published consequence is a system crash without data disclosure or modification.
The record
- CVE
- CVE-2024-40987
- Published
- Jul 12, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 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=a2e73f56fa6282481927ec43aa9362c03c2e2104 <1c44f7759a5650acf8f13d3e0a184d09e03be9e4
- Affected versionversion=a2e73f56fa6282481927ec43aa9362c03c2e2104 <4ad7d49059358ceadd352b4e2511425bdb68f400
- Affected versionversion=a2e73f56fa6282481927ec43aa9362c03c2e2104 <4d020c1dbd2b2304f44d003e6de956ae570049dc
- Affected versionversion=a2e73f56fa6282481927ec43aa9362c03c2e2104 <b065d79ed06a0bb4377bc6dcc2ff0cb1f55a798f
- Affected versionversion=a2e73f56fa6282481927ec43aa9362c03c2e2104 <b0d612619ed70cab476c77b19e00d13aa414e14f
- Affected versionversion=a2e73f56fa6282481927ec43aa9362c03c2e2104 <d8a04a6bfa75251ba7bcc3651ed211e82f13f388
- Affected versionversion=a2e73f56fa6282481927ec43aa9362c03c2e2104 <f0d576f840153392d04b2d52cf3adab8f62e8cb6
- Affected versionversion=a2e73f56fa6282481927ec43aa9362c03c2e2104 <fc5cb952e6723c5c55e47b8cf94a891bd4af1a86
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.
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