Heimdall Security Logo

CVE-2023-53612

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fe, <=6.1.*, e1b370b64031a01bb0c4158ce250073a88921fe1, <5735878a7b7db7e9ce731cb36cec298a9de67549, <6d03bbff456befeccdd4d663177c4d6c75d0c4ff, 6.1.16, 0, <4000384684f612b3645a944f6acde0e65ac370b8, <4.10, 5.10.173, <c57a8d14d7880521150ee801d53a0a64fdffd9c8, <=5.10.*, 4.10, 6.2.3, 6.3, <8fcdbc4bc01365f4b10fed7db544a3149e3054fd, <=5.4.*, 5.15.99, <=6.2.*, 5.4.235, <=*, <=5.15.*

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.

Gravité et risque d'exploitation

CVE-2023-53612 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.14 %, ce qui la place devant 3.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fe, <=6.1.*, e1b370b64031a01bb0c4158ce250073a88921fe1, <5735878a7b7db7e9ce731cb36cec298a9de67549, <6d03bbff456befeccdd4d663177c4d6c75d0c4ff, 6.1.16, 0, <4000384684f612b3645a944f6acde0e65ac370b8, <4.10, 5.10.173, <c57a8d14d7880521150ee801d53a0a64fdffd9c8, <=5.10.*, 4.10, 6.2.3, 6.3, <8fcdbc4bc01365f4b10fed7db544a3149e3054fd, <=5.4.*, 5.15.99, <=6.2.*, 5.4.235, <=*, <=5.15.*) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE