CVE-2026-93142

thermal/drivers/rcar: Fix error checking in probe()

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.9bbcf90c0646ac797700269fa6645a6a46466c79f
Vendor states this is fixed in 35bf61798e7d4abf39667d98f298f793b3dd9bbe (fixed)
Vendor states this is fixed in 623349a18d4c6e6add7876553c0cb6947c8d92e6 (fixed)
Vendor states this is fixed in 810875c5996f731961fc5ee1bd24e711f2e8fe78 (fixed)
Vendor states this is fixed in a85bcd0c7ef66e3404b3c99e5589c5ea622a757e (fixed)
Vendor states this is fixed in d67607e7749527850619a10d3ed033b02dcea516 (fixed)
Vendor states this is fixed in dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d (fixed)
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card