System crash via NULL timing generator dereference
Published May 21, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel AMD display driver allows local users to crash the system through display operations. The dc_stream_get_vblank_counter and dc_stream_get_scanoutpos loops call timing-generator functions after matching a stream without first verifying that stream_res.tg is non-NULL. Low-privileged local access and an affected AMD display configuration are required; the documented consequence is availability loss only.
Summary
What happened
NULL pointer dereference in the Linux kernel AMD display driver allows local users to crash the system through display operations. The dc_stream_get_vblank_counter and dc_stream_get_scanoutpos loops call timing-generator functions after matching a stream without first verifying that stream_res.tg is non-NULL. Low-privileged local access and an affected AMD display configuration are required; the documented consequence is availability loss only.
The record
- CVE
- CVE-2023-52753
- 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.15
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <09909f515032fa80b921fd3118efe66b185d10fd
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <4e497f1acd99075b13605b2e7fa0cba721a2cfd9
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <6d8653b1a7a8dc938b566ae8c4f373b36e792c68
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <79b6a90f4f2433312154cd68452b0ba501fa74db
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <8a06894666e0b462c9316b26ab615cefdd0d676c
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <b1904ed480cee3f9f4036ea0e36d139cb5fee2d6
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <df8bc953eed72371e43ca407bd063507f760cf89
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <eac3e4760aa12159f7f5475d55a67b7933abc195
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