Kernel crash via premature hibmc cleanup
Published Sep 11, 2025 · Updated Sep 11, 2025
NULL pointer dereference in the Linux hibmc DRM driver from 4.14 allows local users to crash the kernel after device initialization fails. The hibmc_load error path calls hibmc_unload after hibmc_hw_init fails, before mode.config mutexes are initialized, so cleanup dereferences a null mutex pointer. Reachability requires local low-privileged access and a HiSilicon hibmc device whose initialization fails; successful triggering crashes the kernel and interrupts the host.
Summary
What happened
NULL pointer dereference in the Linux hibmc DRM driver from 4.14 allows local users to crash the kernel after device initialization fails. The hibmc_load error path calls hibmc_unload after hibmc_hw_init fails, before mode.config mutexes are initialized, so cleanup dereferences a null mutex pointer. Reachability requires local low-privileged access and a HiSilicon hibmc device whose initialization fails; successful triggering crashes the kernel and interrupts the host.
The record
- CVE
- CVE-2025-39772
- Published
- Sep 11, 2025
- Updated
- Sep 11, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 11, 2025CVE publishedPublication date reported by the CVE source.
- Sep 11, 2025Record 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.14
- Affected versionversion=b3df5e65cc03696b0624a877d03a3ddf3ef43f52 <93a08f856fcc5aaeeecad01f71bef3088588216a
- Affected versionversion=b3df5e65cc03696b0624a877d03a3ddf3ef43f52 <a4f1b9c57092c48bdc7958abd23403ccaed437b2
- Affected versionversion=b3df5e65cc03696b0624a877d03a3ddf3ef43f52 <c950e1be3a24d021475b56efdb49daa7fbba63a9
- Affected versionversion=b3df5e65cc03696b0624a877d03a3ddf3ef43f52 <d3e774266c28aefab3e9db334fdf568f936cae04
- Affected versionversion=b3df5e65cc03696b0624a877d03a3ddf3ef43f52 <ddf1691f25345699296e642f0f59f2d464722fa3
- Affected versionversion=b3df5e65cc03696b0624a877d03a3ddf3ef43f52 <f93032e5d68f459601c701f6ab087b5feb3382e8
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.
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