Heimdall Security Logo

CVE-2022-49171

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

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : 5.15.33, <=5.17.*, 2.6.37, 5.18, <5db60e76edf5680ff1f3a7221036fc44b308f146, <2.6.37, <330d0e44fc5a47c27df958ecdd4693a3cb1d8b81, <cc5095747edfb054ca2068d01af20be3fcc3634f, <343117559ef41e992e326f7a92da1a8f254dfa8c, <d666dfaa571465a19f014534a214c255ea33f301, 0, <=4.9.*, <=5.10.*, 4.9.311, <=4.14.*, 5.4.189, <=5.4.*, <=4.19.*, <677c9d30e8487bee6c8e3b034070319d98f6e203, 5.16.19, a42afc5f56f319107e987aa6adf2f65d93d527c7, <=5.16.*, 5.10.110, 4.14.276, 5.17.2, <=*, 4.19.238, <=5.15.*, <5a016c053f426a73752c3b41b60b497b58694d48, <0d3a6926f7e8be3c897fa46216ce13b119a9f56a, <a0856764dc1276ad2dc7891288c2e9246bf11a37

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: don't BUG if someone dirty pages without asking ext4 first [un]pin_user_pages_remote is dirtying pages without properly warning the file system in advance. A related race was noted by Jan Kara in 2018[1]; however, more recently instead of it being a very hard-to-hit race, it could be reliably triggered by process_vm_writev(2) which was discovered by Syzbot[2]. This is technically a bug in mm/gup.c, but arguably ext4 is fragile in that if some other kernel subsystem dirty pages without properly notifying the file system using page_mkwrite(), ext4 will BUG, while other file systems will not BUG (although data will still be lost). So instead of crashing with a BUG, issue a warning (since there may be potential data loss) and just mark the page as clean to avoid unprivileged denial of service attacks until the problem can be properly fixed. More discussion and background can be found in the thread starting at [2]. [1] https://lore.kernel.org/linux-mm/20180103100430.GE4911@quack2.suse.cz [2] https://lore.kernel.org/r/Yg0m6IjcNmfaSokM@google.com

Gravité et risque d'exploitation

CVE-2022-49171 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.28 %, ce qui la place devant 18.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 5.15.33, <=5.17.*, 2.6.37, 5.18, <5db60e76edf5680ff1f3a7221036fc44b308f146, <2.6.37, <330d0e44fc5a47c27df958ecdd4693a3cb1d8b81, <cc5095747edfb054ca2068d01af20be3fcc3634f, <343117559ef41e992e326f7a92da1a8f254dfa8c, <d666dfaa571465a19f014534a214c255ea33f301, 0, <=4.9.*, <=5.10.*, 4.9.311, <=4.14.*, 5.4.189, <=5.4.*, <=4.19.*, <677c9d30e8487bee6c8e3b034070319d98f6e203, 5.16.19, a42afc5f56f319107e987aa6adf2f65d93d527c7, <=5.16.*, 5.10.110, 4.14.276, 5.17.2, <=*, 4.19.238, <=5.15.*, <5a016c053f426a73752c3b41b60b497b58694d48, <0d3a6926f7e8be3c897fa46216ce13b119a9f56a, <a0856764dc1276ad2dc7891288c2e9246bf11a37) 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