# CVE-2026-97475: thermal/drivers/tegra/soctherma: Switch to devm cooling device registration

> A use-after-free vulnerability in the Linux kernel Tegra thermal driver allows attackers to cause denial of service or execute code via improper cooling device cleanup.

- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103833, BELL-CVE-2026-97475, DEBIAN-CVE-2026-97475, GHSA-h37f-mp75-vxqv, UBUNTU-CVE-2026-97475

## What is CVE-2026-97475?

CVE-2026-97475 is an use after free vulnerability in Linux, published on 24 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/tegra/soctherma: Switch to devm cooling device registration

Use devm_thermal_of_cooling_device_register() to simplify resource
management and avoid manual cleanup in error paths.

As a side effect this change has the benefit of solving an existing
issue. Before, the function tegra_soctherm_remove() only called
debugfs_remove_recursive() and never called thermal_cooling_device_unregister()
for any of the cooling devices registered here.

After the driver removal, the thermal framework's cdev list would
still hold references to thermal_cooling_device objects whose devdata
pointer (ts) pointed to memory already freed by the platform device's
devm cleanup.

With this change, the cooling device is unregistered when the driver
is removed, thus fixing the issue above.

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


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

Apply the vendor's patch.

## Is CVE-2026-97475 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97475 is an use after free vulnerability in Linux, published on 24 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-97475 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-97475/ (Markdown: https://insights.sbomify.com/CVE-2026-97475/index.md)
```

## Sources

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

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