System crash via unchecked Radeon voltage index
Published Jul 12, 2024 · Updated May 11, 2026
Out-of-bounds write in affected Linux kernel Radeon releases allows local users to crash the system through an invalid voltage index. sumo_construct_vid_mapping_table() uses table[i].usVoltageIndex to index vid_mapping_table->entries without checking it against SUMO_MAX_NUMBER_VOLTAGES. Exploitation requires local low-privileged access and the affected Radeon power-table path; the reported consequence is service interruption.
Summary
What happened
Out-of-bounds write in affected Linux kernel Radeon releases allows local users to crash the system through an invalid voltage index. sumo_construct_vid_mapping_table() uses table[i].usVoltageIndex to index vid_mapping_table->entries without checking it against SUMO_MAX_NUMBER_VOLTAGES. Exploitation requires local low-privileged access and the affected Radeon power-table path; the reported consequence is service interruption.
The record
- CVE
- CVE-2024-40988
- Published
- Jul 12, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-119, 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=3.11
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <07e8f15fa16695cf4c90e89854e59af4a760055b
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <468a50fd46a09bba7ba18a11054ae64b6479ecdc
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <9e57611182a817824a17b1c3dd300ee74a174b42
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <a498df5421fd737d11bfd152428ba6b1c8538321
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <a8c6df9fe5bc390645d1e96eff14ffe414951aad
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <cf1cc8fcfe517e108794fb711f7faabfca0dc855
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <f803532bc3825384100dfc58873e035d77248447
- Affected versionversion=80ea2c129c76a4159a93efeaef4385b6c964dfac <febe794b83693257f21a23d2e03ea695a62449c8
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