Skip to main content
VulnerabilityPublished Updated

CVE-2026-93142: Linux kernel · thermal/drivers/rcar: Fix error checking in probe()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d, d67607e7749527850619a10d3ed033b02dcea516, a85bcd0c7ef66e3404b3c99e5589c5ea622a757e +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bbcf90c0646ac797700269fa6645a6a46466c79f, < dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d
Fixed in
  • dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d
LinuxLinuxAffected
  • ≥ bbcf90c0646ac797700269fa6645a6a46466c79f, < d67607e7749527850619a10d3ed033b02dcea516
Fixed in
  • d67607e7749527850619a10d3ed033b02dcea516
LinuxLinuxAffected
  • ≥ bbcf90c0646ac797700269fa6645a6a46466c79f, < a85bcd0c7ef66e3404b3c99e5589c5ea622a757e
Fixed in
  • a85bcd0c7ef66e3404b3c99e5589c5ea622a757e
LinuxLinuxAffected
  • ≥ bbcf90c0646ac797700269fa6645a6a46466c79f, < 810875c5996f731961fc5ee1bd24e711f2e8fe78
Fixed in
  • 810875c5996f731961fc5ee1bd24e711f2e8fe78
LinuxLinuxAffected
  • ≥ bbcf90c0646ac797700269fa6645a6a46466c79f, < 623349a18d4c6e6add7876553c0cb6947c8d92e6
Fixed in
  • 623349a18d4c6e6add7876553c0cb6947c8d92e6
LinuxLinuxAffected
  • ≥ bbcf90c0646ac797700269fa6645a6a46466c79f, < 35bf61798e7d4abf39667d98f298f793b3dd9bbe
Fixed in
  • 35bf61798e7d4abf39667d98f298f793b3dd9bbe

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.

References

Community reviews

Loading reviews…