Heimdall Security Logo

CVE-2025-40001

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

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 0, <00d3af40b158ebf7c7db2b3bbb1598a54bf28127, <3c90f583d679c81a5a607a6ae0051251b6dee35b, 6.17.4, 6.18, <=5.10.*, <=6.6.*, <2.6.31, <feb946d2fc9dc754bf3d594d42cd228860ff8647, <c2c35cb2a31844f84f21ab364b38b4309d756d42, <60cd16a3b7439ccb699d0bf533799eeb894fd217, <=5.4.*, 5.15.195, <aacd1777d4a795c387a20b9ca776e2c1225d05d7, 20b09c2992fefbe78f8cede7b404fb143a413c52, <a6f68f219d4d4b92d7c781708d4afc4cc42961ec, 2.6.31, 5.10.246, 6.6.113, <6ba7e73cafd155a5d3abf560d315f0bab2b9d89f, <=*, <=5.15.*, <=6.17.*, 5.4.301, 6.1.157, 6.12.54

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue During the detaching of Marvell's SAS/SATA controller, the original code calls cancel_delayed_work() in mvs_free() to cancel the delayed work item mwq->work_q. However, if mwq->work_q is already running, the cancel_delayed_work() may fail to cancel it. This can lead to use-after-free scenarios where mvs_free() frees the mvs_info while mvs_work_queue() is still executing and attempts to access the already-freed mvs_info. A typical race condition is illustrated below: CPU 0 (remove) | CPU 1 (delayed work callback) mvs_pci_remove() | mvs_free() | mvs_work_queue() cancel_delayed_work() | kfree(mvi) | | mvi-> // UAF Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the delayed work item is properly canceled and any executing delayed work item completes before the mvs_info is deallocated. This bug was found by static analysis.

Gravité et risque d'exploitation

CVE-2025-40001 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.26 %, ce qui la place devant 16.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 0, <00d3af40b158ebf7c7db2b3bbb1598a54bf28127, <3c90f583d679c81a5a607a6ae0051251b6dee35b, 6.17.4, 6.18, <=5.10.*, <=6.6.*, <2.6.31, <feb946d2fc9dc754bf3d594d42cd228860ff8647, <c2c35cb2a31844f84f21ab364b38b4309d756d42, <60cd16a3b7439ccb699d0bf533799eeb894fd217, <=5.4.*, 5.15.195, <aacd1777d4a795c387a20b9ca776e2c1225d05d7, 20b09c2992fefbe78f8cede7b404fb143a413c52, <a6f68f219d4d4b92d7c781708d4afc4cc42961ec, 2.6.31, 5.10.246, 6.6.113, <6ba7e73cafd155a5d3abf560d315f0bab2b9d89f, <=*, <=5.15.*, <=6.17.*, 5.4.301, 6.1.157, 6.12.54) 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