Kernel crash via null CRTC state dereference
Published Jun 25, 2026 · Updated Jun 25, 2026
NULL pointer dereference in affected Linux Kernel branches starting with 5.2 allows local users to crash the kernel through SDP debugfs. The dp_sdp_message_debugfs_write() function dereferences an unchecked CRTC pointer and requests 36 bytes regardless of the supplied write size. Exploitation requires AMD display support, write access to sdp_message, and a connected display with no bound CRTC, such as after hot-plug.
Summary
What happened
NULL pointer dereference in affected Linux Kernel branches starting with 5.2 allows local users to crash the kernel through SDP debugfs. The dp_sdp_message_debugfs_write() function dereferences an unchecked CRTC pointer and requests 36 bytes regardless of the supplied write size. Exploitation requires AMD display support, write access to sdp_message, and a connected display with no bound CRTC, such as after hot-plug.
The record
- CVE
- CVE-2026-53135
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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=5.2
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <7ae95c0275c330b5dbae806f8e431720edad776f
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <7fc4fab4acc307ad2903312c195872b2953d32c3
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <a2de1d71891a038a9346b2c1a72b88c8350f2479
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <adf67034b1f61f7119295208085bfd43f85f56af
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <b781f90a9528555c709e59789550893581ef0be4
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <bb6f705b73b5f191f14ad004e2c8c4b615806187
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <c90954cdea4d6998ec345de0d840d030c145b89e
- Affected versionversion=c7ba3653e9773256b2b08508a2ed2ca28ea7566b <ee9cfcf77a8e8af637396dc00966df5f701e661c
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