CVE-2025-22072

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <=6.14.*, 0, <903733782f3ae28a2f7fe4dfb47c7fe3e079a528, <c134deabf4784e155d360744d4a6a835b9de4dd4, 6.14.2, 6.1.134, <324f280806aab28ef757aecc18df419676c10ef8, <=6.6.*, 6.6.87, 6.13.11, 877907d37da9694a34adc9dc3e2ce09400148cb5, 6.12.23, <fc646a6c6d14b5d581f162a7e32999f789e3a3ac, <2.6.22, 2.6.22, <029d8c711f5e5fe8cf63e8a4a1a140a06e224e45, 6.15, <=*, <=6.13.*, <880e7b3da2e765c1f90c94c0539be039e96c7062

Description

In the Linux kernel, the following vulnerability has been resolved: spufs: fix gang directory lifetimes prior to "[POWERPC] spufs: Fix gang destroy leaks" we used to have a problem with gang lifetimes - creation of a gang returns opened gang directory, which normally gets removed when that gets closed, but if somebody has created a context belonging to that gang and kept it alive until the gang got closed, removal failed and we ended up with a leak. Unfortunately, it had been fixed the wrong way. Dentry of gang directory was no longer pinned, and rmdir on close was gone. One problem was that failure of open kept calling simple_rmdir() as cleanup, which meant an unbalanced dput(). Another bug was in the success case - gang creation incremented link count on root directory, but that was no longer undone when gang got destroyed. Fix consists of * reverting the commit in question * adding a counter to gang, protected by ->i_rwsem of gang directory inode. * having it set to 1 at creation time, dropped in both spufs_dir_close() and spufs_gang_close() and bumped in spufs_create_context(), provided that it's not 0. * using simple_recursive_removal() to take the gang directory out when counter reaches zero.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <=6.14.*, 0, <903733782f3ae28a2f7fe4dfb47c7fe3e079a528, <c134deabf4784e155d360744d4a6a835b9de4dd4, 6.14.2, 6.1.134, <324f280806aab28ef757aecc18df419676c10ef8, <=6.6.*, 6.6.87, 6.13.11, 877907d37da9694a34adc9dc3e2ce09400148cb5, 6.12.23, <fc646a6c6d14b5d581f162a7e32999f789e3a3ac, <2.6.22, 2.6.22, <029d8c711f5e5fe8cf63e8a4a1a140a06e224e45, 6.15, <=*, <=6.13.*, <880e7b3da2e765c1f90c94c0539be039e96c7062) 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