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-2023-53612hwmon: (coretemp) Simplify platform device handling

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Simplify platform device handling Coretemp's platform driver is unconventional. All the real work is done globally by the initcall and CPU hotplug notifiers, while the "driver" effectively just wraps an allocation and the registration of the hwmon interface in a long-winded round-trip through the driver core. The whole logic of dynamically creating and destroying platform devices to bring the interfaces up and down is error prone, since it assumes platform_device_add() will synchronously bind the driver and set drvdata before it returns, thus results in a NULL dereference if drivers_autoprobe is turned off for the platform bus. Furthermore, the unusual approach of doing that from within a CPU hotplug notifier, already commented in the code that it deadlocks suspend, also causes lockdep issues for other drivers or subsystems which may want to legitimately register a CPU hotplug notifier from a platform bus notifier. All of these issues can be solved by ripping this unusual behaviour out completely, simply tying the platform devices to the lifetime of the module itself, and directly managing the hwmon interfaces from the hotplug notifiers. There is a slight user-visible change in that /sys/bus/platform/drivers/coretemp will no longer appear, and /sys/devices/platform/coretemp.n will remain present if package n is hotplugged off, but hwmon users should really only be looking for the presence of the hwmon interfaces, whose behaviour remains unchanged.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 months 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

CVSS scores of CVE-2023-53612, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e1b370b64031a01bb0c4158ce250073a88921fe1 – < 4000384684f612b3645a944f6acde0e65ac370b8
    • affected e1b370b64031a01bb0c4158ce250073a88921fe1 – < 5735878a7b7db7e9ce731cb36cec298a9de67549
    • affected e1b370b64031a01bb0c4158ce250073a88921fe1 – < 52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fe
    • affected e1b370b64031a01bb0c4158ce250073a88921fe1 – < 8fcdbc4bc01365f4b10fed7db544a3149e3054fd
    • affected e1b370b64031a01bb0c4158ce250073a88921fe1 – < c57a8d14d7880521150ee801d53a0a64fdffd9c8
    • affected e1b370b64031a01bb0c4158ce250073a88921fe1 – < 6d03bbff456befeccdd4d663177c4d6c75d0c4ff
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 5.4.235 – ≤ 5.4.*
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.99 – ≤ 5.15.*
    • unaffected 6.1.16 – ≤ 6.1.*
    • unaffected 6.2.3 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .