CVE-2025-21915

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 6.4, 6.6.83, <=*, 6.12.19, <=6.12.*, 6.14, <91d44c1afc61a2fec37a9c7a3485368309391e0b, 6.13.7, <=6.6.*, <d7b339bbc887bcfc1a5b620bfc70c6fbb8f733bf, <6.4, 0, <=6.13.*, <8473135f89c0949436a22adb05b8cece2fb3da91, <0439d541aa8d3444ad41c39e39eb71acb57acde3, 2959ab247061e67485d83b6af8feb3761ec08cb9

Description

In the Linux kernel, the following vulnerability has been resolved: cdx: Fix possible UAF error in driver_override_show() Fixed a possible UAF problem in driver_override_show() in drivers/cdx/cdx.c This function driver_override_show() is part of DEVICE_ATTR_RW, which includes both driver_override_show() and driver_override_store(). These functions can be executed concurrently in sysfs. The driver_override_store() function uses driver_set_override() to update the driver_override value, and driver_set_override() internally locks the device (device_lock(dev)). If driver_override_show() reads cdx_dev->driver_override without locking, it could potentially access a freed pointer if driver_override_store() frees the string concurrently. This could lead to printing a kernel address, which is a security risk since DEVICE_ATTR can be read by all users. Additionally, a similar pattern is used in drivers/amba/bus.c, as well as many other bus drivers, where device_lock() is taken in the show function, and it has been working without issues. This potential bug was detected by our experimental static analysis tool, which analyzes locking APIs and paired functions to identify data races and atomicity violations.

Gravité et risque d'exploitation

CVE-2025-21915 obtient un score CVSS de 7.8/10, soit une gravité élevé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 9.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.4, 6.6.83, <=*, 6.12.19, <=6.12.*, 6.14, <91d44c1afc61a2fec37a9c7a3485368309391e0b, 6.13.7, <=6.6.*, <d7b339bbc887bcfc1a5b620bfc70c6fbb8f733bf, <6.4, 0, <=6.13.*, <8473135f89c0949436a22adb05b8cece2fb3da91, <0439d541aa8d3444ad41c39e39eb71acb57acde3, 2959ab247061e67485d83b6af8feb3761ec08cb9) 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