Kernel memory exposure via unchecked firmware identifier
Published Sep 18, 2024 · Updated May 11, 2026
Out-of-bounds read in the Linux kernel amdgpu driver allows local users to read kernel memory through a firmware information request. The amdgpu_cgs_get_firmware_info function uses the identifier returned by fw_type_convert to index adev->firmware.ucode without first rejecting values at or above AMDGPU_UCODE_ID_MAXIMUM. An attacker needs local access and an AMD GPU that reaches this firmware lookup; the invalid array access can expose kernel memory or crash the system.
Summary
What happened
Out-of-bounds read in the Linux kernel amdgpu driver allows local users to read kernel memory through a firmware information request. The amdgpu_cgs_get_firmware_info function uses the identifier returned by fw_type_convert to index adev->firmware.ucode without first rejecting values at or above AMDGPU_UCODE_ID_MAXIMUM. An attacker needs local access and an AMD GPU that reaches this firmware lookup; the invalid array access can expose kernel memory or crash the system.
The record
- CVE
- CVE-2024-46723
- Published
- Sep 18, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 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 <0bef65e069d84d1cd77ce757aea0e437b8e2bd33
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <23fefef859c6057e6770584242bdd938254f8ddd
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <5f09fa5e0ad45fbca71933a0e024ca52da47d59b
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <82ac8f1d02886b5d8aeb9e058989d3bd6fc581e2
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <8944acd0f9db33e17f387fdc75d33bb473d7936f
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <8981927ebc6c12fa76b30c4178acb462bab15f54
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <e789e05388854a5436b2b5d8695fdb864c9bcc27
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <f2b7a9f3839e92f43559b2795b34640ca8cf839f
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