CVE-2026-93081

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 9ca67840c0ddf3f39407339624cef824a4f27599, 6.6.90, 91ff1e9652fb9beb0174267d6bb38243dff211bb, 5.15.182, <6.13, 0, ff4273d47da81b95ed9396110bcbd1b7b7470fe8, <a60bc2df2d323cc1342f0cf95563cae266801e20, 6.18.57, <6abe8fe36b29ff51d1a42c2f338972883f4751a5, 6.1.138, 7.2.6, 969d8beaa2e374387bf9aa5602ef84fc50bb48d8, <5.16, <c59b3393df1348a12308aaabd5fbc58ed6b21cf5, <=6.18.*, 6.14.6, <6.2, 8a8a3547d5c4960da053df49c75bf623827a25da, 6.15, <=7.2.*, <6.7, <=*, <6.15, 2fbf6c9695ad9f05e7e5c166bf43fac7cb3276b3, 6.12.28, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Fix SCMI device destroy lifetimes scmi_child_dev_find() drops the reference returned by device_find_child() before returning the scmi_device pointer. A concurrent unregister can then release the device while the destroy path is still using the returned pointer. Make the lookup helper return the device_find_child() reference and keep it until scmi_device_destroy() has finished unregistering the child. Also split device_unregister() in __scmi_device_destroy() so the SCMI bus ID is not made reusable until after device_del() has removed the old scmi_dev.N name from sysfs. This avoids a new SCMI device reusing the same ID while the old device is still registered. The final device release callback is also a possible cleanup path when SCMI children are deleted by driver core recursion rather than __scmi_device_destroy(). Release the SCMI bus ID from a common helper used by destroy, register-failure and final-release paths, and clear scmi_dev->id after freeing it so the final release cannot free the same ID again.

Gravité et risque d'exploitation

CVE-2026-93081 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.20 %, ce qui la place devant 8.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 9ca67840c0ddf3f39407339624cef824a4f27599, 6.6.90, 91ff1e9652fb9beb0174267d6bb38243dff211bb, 5.15.182, <6.13, 0, ff4273d47da81b95ed9396110bcbd1b7b7470fe8, <a60bc2df2d323cc1342f0cf95563cae266801e20, 6.18.57, <6abe8fe36b29ff51d1a42c2f338972883f4751a5, 6.1.138, 7.2.6, 969d8beaa2e374387bf9aa5602ef84fc50bb48d8, <5.16, <c59b3393df1348a12308aaabd5fbc58ed6b21cf5, <=6.18.*, 6.14.6, <6.2, 8a8a3547d5c4960da053df49c75bf623827a25da, 6.15, <=7.2.*, <6.7, <=*, <6.15, 2fbf6c9695ad9f05e7e5c166bf43fac7cb3276b3, 6.12.28, 7.3) 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