thermal/drivers/tegra/soctherma: Switch to devm cooling device registration
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ce0dbf04f685d48ffdec64a17ebb4965f828c3ff · < deaeb7be8e6b04c8b71080acba1bd88698f56b1d| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Tegra thermal driver fails to unregister cooling devices when it is removed, leaving the thermal framework with references to objects whose driver data has been freed. The input does not specify how an attacker could trigger driver removal or exploit these references, or whether authentication or user interaction is required.
Engineers running Linux kernels with the Tegra thermal driver should check their versions; affected versions are not specified.