CVE-2026-97475

thermal/drivers/tegra/soctherma: Switch to devm cooling device registration

N/A
Published: September 24, 2026 at 04:04 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.9 ≤ v < 5.10.2714.9 ≤ v < 5.15.2224.9 ≤ v < 6.1.1894.9 ≤ v < 6.12.1114.9 ≤ v < 6.18.534.9 ≤ v < 6.6.1584.9 ≤ v < 7.24.9ce0dbf04f685d48ffdec64a17ebb4965f828c3ff
Vendor states this is fixed in 0c65f786a69402620306828aa19817fd71f37f4b (fixed)
Vendor states this is fixed in 6f2a863e7e9adf6088fe644259576181e60ee5e5 (fixed)
Vendor states this is fixed in 78a2ba09fd7501df09239c7e3c311c80c259ed31 (fixed)
Vendor states this is fixed in a643ce49ddcdbdec173e7bbf4c32c897e0293ba9 (fixed)
Vendor states this is fixed in deaeb7be8e6b04c8b71080acba1bd88698f56b1d (fixed)
Vendor states this is fixed in e777ab46db8c2addffe801274d713252318ef750 (fixed)
Vendor states this is fixed in ee126267bc04bfb03816ae9d71ca24c5bf99e739 (fixed)
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card