GHSA-H37F-MP75-VXQV
Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-24 18:31In 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": [],
"aliases": [
"CVE-2026-97475"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-24T17:17:24Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nthermal/drivers/tegra/soctherma: Switch to devm cooling device registration\n\nUse devm_thermal_of_cooling_device_register() to simplify resource\nmanagement and avoid manual cleanup in error paths.\n\nAs a side effect this change has the benefit of solving an existing\nissue. Before, the function tegra_soctherm_remove() only called\ndebugfs_remove_recursive() and never called thermal_cooling_device_unregister()\nfor any of the cooling devices registered here.\n\nAfter the driver removal, the thermal framework\u0027s cdev list would\nstill hold references to thermal_cooling_device objects whose devdata\npointer (ts) pointed to memory already freed by the platform device\u0027s\ndevm cleanup.\n\nWith this change, the cooling device is unregistered when the driver\nis removed, thus fixing the issue above.",
"id": "GHSA-h37f-mp75-vxqv",
"modified": "2026-09-24T18:31:34Z",
"published": "2026-09-24T18:31:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97475"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6f2a863e7e9adf6088fe644259576181e60ee5e5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/deaeb7be8e6b04c8b71080acba1bd88698f56b1d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee126267bc04bfb03816ae9d71ca24c5bf99e739"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.