thermal/drivers/rcar: Fix error checking in probe()
Summary
| CVE | CVE-2026-93142 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:18:09 UTC |
| Updated | 2026-10-19 10:17:04 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/rcar: Fix error checking in probe() This code accidentally calls thermal_zone_device_enable() before checking whether thermal_zone_device_register_with_trips() failed. Move the call until later to avoid an error pointer dereference of "priv->zone". The driver works differently depending on if we are using OF thermal or not. We use thermal_add_hwmon_sysfs() if we are using OF thermal and call thermal_zone_device_enable() if not. We can share same error check for if either of these fail. Moving the thermal_zone_device_enable() call is a bit cleaner as well. The original code used a three step process to cleanup: 1. Call thermal_zone_device_unregister() to cleanup. 2. Set priv->zone to an error pointer to preserve the error code. 3. Set priv->zone to NULL to avoid a second call to thermal_zone_device_unregister() in the rcar_thermal_remove() function. Now we can just do a direct goto error_unregister and rcar_thermal_remove() handles the cleanup properly. |
Risk And Classification
EPSS: 0.002150000 probability, percentile 0.121610000 (date 2026-09-18)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected bbcf90c0646ac797700269fa6645a6a46466c79f a85bcd0c7ef66e3404b3c99e5589c5ea622a757e git | Not specified |
| CNA | Linux | Linux | affected bbcf90c0646ac797700269fa6645a6a46466c79f 810875c5996f731961fc5ee1bd24e711f2e8fe78 git | Not specified |
| CNA | Linux | Linux | affected bbcf90c0646ac797700269fa6645a6a46466c79f 623349a18d4c6e6add7876553c0cb6947c8d92e6 git | Not specified |
| CNA | Linux | Linux | affected bbcf90c0646ac797700269fa6645a6a46466c79f 35bf61798e7d4abf39667d98f298f793b3dd9bbe git | Not specified |
| CNA | Linux | Linux | affected bbcf90c0646ac797700269fa6645a6a46466c79f d67607e7749527850619a10d3ed033b02dcea516 git | Not specified |
| CNA | Linux | Linux | affected bbcf90c0646ac797700269fa6645a6a46466c79f dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d git | Not specified |
| CNA | Linux | Linux | affected 5.9 | Not specified |
| CNA | Linux | Linux | unaffected 5.9 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.188 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.157 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.110 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.52 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.6 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/35bf61798e7d4abf39667d98f298f793b3dd9bbe | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a85bcd0c7ef66e3404b3c99e5589c5ea622a757e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/810875c5996f731961fc5ee1bd24e711f2e8fe78 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/623349a18d4c6e6add7876553c0cb6947c8d92e6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d67607e7749527850619a10d3ed033b02dcea516 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.