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

> A null pointer dereference in the Linux kernel rcar thermal driver probe function can cause a system crash, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102708, BELL-CVE-2026-93142, DEBIAN-CVE-2026-93142, GHSA-hm78-cgjx-c8pf, UBUNTU-CVE-2026-93142

## What is CVE-2026-93142?

CVE-2026-93142 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-93142?


## How do I fix CVE-2026-93142?

Apply the vendor's patch.

## Is CVE-2026-93142 being exploited?

There is no known exploitation of CVE-2026-93142 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93142 and fix it if it is affected.

What it is: CVE-2026-93142 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93142 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93142/ (Markdown: https://insights.sbomify.com/CVE-2026-93142/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93142
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93142
- OSV: https://osv.dev/vulnerability/CVE-2026-93142

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93142/
Summaries are generated and may contain mistakes; the official description above is the record.