Heimdall Security Logo

CVE-2022-50379

Vulnérabilité moyenne dans Linux (Linux)

CVSS 4.7 · Moyenne
EPSS 0.1%
Linux•Linux•Versions : <4b996a3014ef014af8f97b60c35f5289210a4720, <c97f6d528c3f1c83a6b792a8a7928c236c80b8fe, <0efd9dfc00d677a1d0929319a6103cb2dfc41c22, 0, <331cd9461412e103d07595a10289de90004ac890, 4.19.262, 5.4.220, <4.17, <=5.10.*, <=6.0.*, 4.17, <=5.4.*, <6c22f86dd221eba0c7af645b1af73dcbc04ee27b, <26b7c0ac49a3eea15559c9d84863736a6d1164b4, <=4.19.*, <47b5ffe86332af95f0f52be0a63d4da7c2b37b55, 5d23515be66904fa3b1b5d6bd72d2199cd2447ab, 6.1, 5.19.17, <=*, <=5.15.*, 6.0.3, <=5.19.*, 5.15.75, 5.10.150

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota rescan ioctl When enabling quotas, at btrfs_quota_enable(), after committing the transaction, we change fs_info->quota_root to point to the quota root we created and set BTRFS_FS_QUOTA_ENABLED at fs_info->flags. Then we try to start the qgroup rescan worker, first by initializing it with a call to qgroup_rescan_init() - however if that fails we end up freeing the quota root but we leave fs_info->quota_root still pointing to it, this can later result in a use-after-free somewhere else. We have previously set the flags BTRFS_FS_QUOTA_ENABLED and BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at btrfs_quota_enable(), which is possible if someone already called the quota rescan ioctl, and therefore started the rescan worker. So fix this by ignoring an -EINPROGRESS and asserting we can't get any other error.

Gravité et risque d'exploitation

CVE-2022-50379 obtient un score CVSS de 4.7/10, soit une gravité moyenne. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.11 %, ce qui la place devant 1.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <4b996a3014ef014af8f97b60c35f5289210a4720, <c97f6d528c3f1c83a6b792a8a7928c236c80b8fe, <0efd9dfc00d677a1d0929319a6103cb2dfc41c22, 0, <331cd9461412e103d07595a10289de90004ac890, 4.19.262, 5.4.220, <4.17, <=5.10.*, <=6.0.*, 4.17, <=5.4.*, <6c22f86dd221eba0c7af645b1af73dcbc04ee27b, <26b7c0ac49a3eea15559c9d84863736a6d1164b4, <=4.19.*, <47b5ffe86332af95f0f52be0a63d4da7c2b37b55, 5d23515be66904fa3b1b5d6bd72d2199cd2447ab, 6.1, 5.19.17, <=*, <=5.15.*, 6.0.3, <=5.19.*, 5.15.75, 5.10.150) 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