Kernel crash via unchecked AMD GPU resource pointer
Published Jun 20, 2024 · Updated May 11, 2026
NULL pointer dereference in AMD GPU virtual-memory updates in Linux 6.4 through 6.5.8 allows local users to crash the kernel. The amdgpu_vm_bo_update function reads abo->tbo.resource->mem_type without first verifying that the resource pointer is non-NULL. Reachability requires the affected AMD GPU path and, under SUSE's assessment, high local privileges; the reported consequence is availability loss only.
Summary
What happened
NULL pointer dereference in AMD GPU virtual-memory updates in Linux 6.4 through 6.5.8 allows local users to crash the kernel. The amdgpu_vm_bo_update function reads abo->tbo.resource->mem_type without first verifying that the resource pointer is non-NULL. Reachability requires the affected AMD GPU path and, under SUSE's assessment, high local privileges; the reported consequence is availability loss only.
The record
- CVE
- CVE-2023-52883
- Published
- Jun 20, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 20, 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=1802537820389183dfcd814e0f6a60d1496a75ef <51b79f33817544e3b4df838d86e8e8e4388ff684
- Affected versionversion=1802537820389183dfcd814e0f6a60d1496a75ef <fefac8c4686fd81fde6830c6dae32f9001d2ac28
- Affected versionversion=6.4
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