CVE-2025-38584

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

CVSS 7.0 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <71203f68c7749609d7fc8ae6ad054bdedeb24f91, <=6.12.*, <=6.16.*, 6.17, 0, <2.6.34, <=6.15.*, <a2048e475e22b13dc3e53d485b7e6e11464ed9a6, 5.15.209, <=5.10.*, <=6.6.*, 6.1.175, <73f132e60857038416540c3599b1de6033d7575a, 6.16.1, <609e59193fc6d9dd323f1c6ae1fdd721f1c79680, 2.6.34, <a11a12a9880ab37342b73c93cfe1a3ada02ff0db, 5.10.258, 6.15.10, 16295bec6398a3eedc9377e1af6ff4c71b98c300, <=*, <f231d5d001ec75f5886c02d496a4c79edc383d45, <=5.15.*, <dbe3e911a59bda6de96e7cae387ff882c2c177fa, 6.6.140, 6.12.86, <cdf79bd2e1ecb3cc75631c73d8f4149be6019a52

Description

In the Linux kernel, the following vulnerability has been resolved: padata: Fix pd UAF once and for all There is a race condition/UAF in padata_reorder that goes back to the initial commit. A reference count is taken at the start of the process in padata_do_parallel, and released at the end in padata_serial_worker. This reference count is (and only is) required for padata_replace to function correctly. If padata_replace is never called then there is no issue. In the function padata_reorder which serves as the core of padata, as soon as padata is added to queue->serial.list, and the associated spin lock released, that padata may be processed and the reference count on pd would go away. Fix this by getting the next padata before the squeue->serial lock is released. In order to make this possible, simplify padata_reorder by only calling it once the next padata arrives.

Gravité et risque d'exploitation

CVE-2025-38584 obtient un score CVSS de 7.0/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.18 %, ce qui la place devant 7.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <71203f68c7749609d7fc8ae6ad054bdedeb24f91, <=6.12.*, <=6.16.*, 6.17, 0, <2.6.34, <=6.15.*, <a2048e475e22b13dc3e53d485b7e6e11464ed9a6, 5.15.209, <=5.10.*, <=6.6.*, 6.1.175, <73f132e60857038416540c3599b1de6033d7575a, 6.16.1, <609e59193fc6d9dd323f1c6ae1fdd721f1c79680, 2.6.34, <a11a12a9880ab37342b73c93cfe1a3ada02ff0db, 5.10.258, 6.15.10, 16295bec6398a3eedc9377e1af6ff4c71b98c300, <=*, <f231d5d001ec75f5886c02d496a4c79edc383d45, <=5.15.*, <dbe3e911a59bda6de96e7cae387ff882c2c177fa, 6.6.140, 6.12.86, <cdf79bd2e1ecb3cc75631c73d8f4149be6019a52) 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