Kernel crash via unsynchronized GPU reset interrupts
Published Jul 25, 2025 · Updated May 11, 2026
NULL pointer dereference in the V3D DRM driver in affected Linux kernels allows local users to crash the system during a GPU reset. The v3d_reset path resets GPU state without first masking and synchronizing V3D interrupt handlers, allowing v3d_irq to run against cleared state. Exploitation requires low-privileged local access and a V3D GPU; the bounded consequence is a GPU hang or availability-only kernel panic.
Summary
What happened
NULL pointer dereference in the V3D DRM driver in affected Linux kernels allows local users to crash the system during a GPU reset. The v3d_reset path resets GPU state without first masking and synchronizing V3D interrupt handlers, allowing v3d_irq to run against cleared state. Exploitation requires low-privileged local access and a V3D GPU; the bounded consequence is a GPU hang or availability-only kernel panic.
The record
- CVE
- CVE-2025-38371
- Published
- Jul 25, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- 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=4.18
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <226862f50a7a88e4e4de9abbf36c64d19acd6fd0
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <2446e25e9246e0642a41d91cbf54c33b275da3c3
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <387da3b6d1a90e3210bc9a7fb56703bdad2ac18a
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <576a6739e08ac06c67f2916f71204557232388b0
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <9ff95ed0371aec4d9617e478e9c69cde86cd7c38
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <b9c403d1236cecb10dd0246a30d81e4b265f8e8d
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <c8851a6ab19d9f390677c42a3cc01ff9b2eb6241
- Affected versionversion=57692c94dcbe99a1e0444409a3da13fb3443562c <dc805c927cd832bb8f790b756880ae6c769d5fbc
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.
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