Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ce0dbf04f685d48ffdec64a17ebb4965f828c3ff – < 78a2ba09fd7501df09239c7e3c311c80c259ed31
    • affected ce0dbf04f685d48ffdec64a17ebb4965f828c3ff – < 0c65f786a69402620306828aa19817fd71f37f4b
    • affected ce0dbf04f685d48ffdec64a17ebb4965f828c3ff – < e777ab46db8c2addffe801274d713252318ef750
    • affected ce0dbf04f685d48ffdec64a17ebb4965f828c3ff – < a643ce49ddcdbdec173e7bbf4c32c897e0293ba9
    • affected ce0dbf04f685d48ffdec64a17ebb4965f828c3ff – < 6f2a863e7e9adf6088fe644259576181e60ee5e5
    • affected ce0dbf04f685d48ffdec64a17ebb4965f828c3ff – < deaeb7be8e6b04c8b71080acba1bd88698f56b1d
    • affected ce0dbf04f685d48ffdec64a17ebb4965f828c3ff – < ee126267bc04bfb03816ae9d71ca24c5bf99e739
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97475 badge
[![CVE-2026-97475](https://cveledger.app/badge/CVE-2026-97475.svg)](https://cveledger.app/cve/CVE-2026-97475)

Record last updated .