Local crash via unchecked CRTC state allocation
Published Jul 25, 2025 · Updated May 11, 2026
Affected Linux kernel releases starting at 5.3 allow local users to crash a Tegra display system during CRTC reset. The tegra_crtc_reset() path passes the unchecked result of kzalloc() to __drm_atomic_helper_crtc_reset(), which dereferences a null state pointer after allocation failure. Triggering the crash requires local low-privileged access to a system using the Tegra DRM driver and an allocation failure during reset.
Summary
What happened
Affected Linux kernel releases starting at 5.3 allow local users to crash a Tegra display system during CRTC reset. The tegra_crtc_reset() path passes the unchecked result of kzalloc() to __drm_atomic_helper_crtc_reset(), which dereferences a null state pointer after allocation failure. Triggering the crash requires local low-privileged access to a system using the Tegra DRM driver and an allocation failure during reset.
The record
- CVE
- CVE-2025-38363
- Published
- Jul 25, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2025CVE 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=5.3
- Affected versionversion=b7e0b04ae450a0f2f73c376c3057fb05d798e33c <31ac2c680a8ac11dc54a5b339a07e138bcedd924
- Affected versionversion=b7e0b04ae450a0f2f73c376c3057fb05d798e33c <5ff3636bcc32e1cb747f6f820bcf2bb6990a7d41
- Affected versionversion=b7e0b04ae450a0f2f73c376c3057fb05d798e33c <780351a5f61416ed2ba1199cc57e4a076fca644d
- Affected versionversion=b7e0b04ae450a0f2f73c376c3057fb05d798e33c <99a25fc7933b88d5e16668bf6ba2d098e1754406
- Affected versionversion=b7e0b04ae450a0f2f73c376c3057fb05d798e33c <ab390ab81241cf8bf37c0a0ac2e9c6606bf3e991
- Affected versionversion=b7e0b04ae450a0f2f73c376c3057fb05d798e33c <ac4ca634f0c9f227538711d725339293f7047b02
- Affected versionversion=b7e0b04ae450a0f2f73c376c3057fb05d798e33c <c7fc459ae6f988e0d5045a270bd600ab08bc61f1
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