CVE-2025-39759

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

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 6.12.44, <=6.16.*, <c38028ce0d0045ca600b6a8345a0ff92bfb47b66, 6.17, 0, 3.12, <dd0b28d877b293b1d7f8727a7de08ae36b6b9ef0, <e1249667750399a48cafcf5945761d39fa584edf, <b172535ccba12f0cf7d23b3b840989de47fc104d, 6.6.103, <=6.15.*, <=6.6.*, <2fd0f5ceb997f90f4332ccbab6c7e907e6b2d0eb, e685da14af6b31e4b336a110cb1bae1afc268be8, 6.1.149, 6.16.2, <3.12, <=*, 6.15.11, <7cda0fdde5d9890976861421d207870500f9aace

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix race between quota disable and quota rescan ioctl There's a race between a task disabling quotas and another running the rescan ioctl that can result in a use-after-free of qgroup records from the fs_info->qgroup_tree rbtree. This happens as follows: 1) Task A enters btrfs_ioctl_quota_rescan() -> btrfs_qgroup_rescan(); 2) Task B enters btrfs_quota_disable() and calls btrfs_qgroup_wait_for_completion(), which does nothing because at that point fs_info->qgroup_rescan_running is false (it wasn't set yet by task A); 3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups from fs_info->qgroup_tree without taking the lock fs_info->qgroup_lock; 4) Task A enters qgroup_rescan_zero_tracking() which starts iterating the fs_info->qgroup_tree tree while holding fs_info->qgroup_lock, but task B is freeing qgroup records from that tree without holding the lock, resulting in a use-after-free. Fix this by taking fs_info->qgroup_lock at btrfs_free_qgroup_config(). Also at btrfs_qgroup_rescan() don't start the rescan worker if quotas were already disabled.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.12.44, <=6.16.*, <c38028ce0d0045ca600b6a8345a0ff92bfb47b66, 6.17, 0, 3.12, <dd0b28d877b293b1d7f8727a7de08ae36b6b9ef0, <e1249667750399a48cafcf5945761d39fa584edf, <b172535ccba12f0cf7d23b3b840989de47fc104d, 6.6.103, <=6.15.*, <=6.6.*, <2fd0f5ceb997f90f4332ccbab6c7e907e6b2d0eb, e685da14af6b31e4b336a110cb1bae1afc268be8, 6.1.149, 6.16.2, <3.12, <=*, 6.15.11, <7cda0fdde5d9890976861421d207870500f9aace) 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