Kernel crash via unchecked smc_rreg callback
Published May 21, 2024 · Updated May 11, 2026
NULL pointer dereference in affected Linux kernel releases allows local users to crash the kernel by reading an amdgpu debugfs file. amdgpu_debugfs_regs_smc_read invokes the device's smc_rreg callback without first checking whether the function pointer is NULL. Local access to the debugfs file and affected AMD GPU hardware such as VEGA20 are required; triggering the flaw causes a kernel oops and service interruption.
Summary
What happened
NULL pointer dereference in affected Linux kernel releases allows local users to crash the kernel by reading an amdgpu debugfs file. amdgpu_debugfs_regs_smc_read invokes the device's smc_rreg callback without first checking whether the function pointer is NULL. Local access to the debugfs file and affected AMD GPU hardware such as VEGA20 are required; triggering the flaw causes a kernel oops and service interruption.
The record
- CVE
- CVE-2023-52817
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 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 <174f62a0aa15c211e60208b41ee9e7cdfb73d455
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <437e0fa907ba39b4d7eda863c03ea9cf48bd93a9
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <5104fdf50d326db2c1a994f8b35dcd46e63ae4ad
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <6c1b3d89a2dda79881726bb6e37af19c0936d736
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <820daf9ffe2b0afb804567b10983fb38bc5ae288
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <ba3c0796d292de84f2932cc5bbb0f771fc720996
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <bf2d51eedf03bd61e3556e35d74d49e2e6112398
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <f475d5502f33a6c5b149b0afe96316ad1962a64a
What conditions does exploitation require?
What is affected?
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