Kernel crash via unchecked thermal-zone registration failure
Published Sep 17, 2026 · Updated Sep 17, 2026
Error-pointer dereference in Linux's R-Car thermal driver allows local users to crash the kernel during failed thermal-zone registration. The probe routine calls thermal_zone_device_enable() on priv->zone before checking whether thermal_zone_device_register_with_trips() returned an error pointer. The failure requires the affected driver initialization path without OF thermal and unsuccessful registration; public upstream evidence does not establish an attacker-controlled registration-failure trigger.
Summary
What happened
Error-pointer dereference in Linux's R-Car thermal driver allows local users to crash the kernel during failed thermal-zone registration. The probe routine calls thermal_zone_device_enable() on priv->zone before checking whether thermal_zone_device_register_with_trips() returned an error pointer. The failure requires the affected driver initialization path without OF thermal and unsuccessful registration; public upstream evidence does not establish an attacker-controlled registration-failure trigger.
The record
- CVE
- CVE-2026-93142
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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.9
- Affected versionversion=bbcf90c0646ac797700269fa6645a6a46466c79f <35bf61798e7d4abf39667d98f298f793b3dd9bbe
- Affected versionversion=bbcf90c0646ac797700269fa6645a6a46466c79f <623349a18d4c6e6add7876553c0cb6947c8d92e6
- Affected versionversion=bbcf90c0646ac797700269fa6645a6a46466c79f <810875c5996f731961fc5ee1bd24e711f2e8fe78
- Affected versionversion=bbcf90c0646ac797700269fa6645a6a46466c79f <a85bcd0c7ef66e3404b3c99e5589c5ea622a757e
- Affected versionversion=bbcf90c0646ac797700269fa6645a6a46466c79f <d67607e7749527850619a10d3ed033b02dcea516
- Affected versionversion=bbcf90c0646ac797700269fa6645a6a46466c79f <dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started