Heimdall Security Logo

CVE-2024-47674

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959, <65d0db500d7c07f0f76fc24a4d837791c4862cd2, <5.13, 6.6.52, 69d4e1ce9087c8767f2fe9b9426fa2755c8e9072, 0, <35770ca6180caa24a2b258c99a87bd437a1ee10f, <a95a24fcaee1b892e47d5e6dcc403f713874ee80, <=6.6.*, <79a61cc3fc0466ad2b7b89618a6157785f0293b3, 6.1.111, 5.13, <954fd4c81f22c4b6ba65379a81fd252971bf4ef3, 6.10.11, 6.11, <=*, b97a50adb37e98b940a30c4656565ff609aa8f94, <=5.15.*, <3213fdcab961026203dd587a4533600c70b3336b, 5.15.168, 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e, <=6.10.*

Description

In the Linux kernel, the following vulnerability has been resolved: mm: avoid leaving partial pfn mappings around in error case As Jann points out, PFN mappings are special, because unlike normal memory mappings, there is no lifetime information associated with the mapping - it is just a raw mapping of PFNs with no reference counting of a 'struct page'. That's all very much intentional, but it does mean that it's easy to mess up the cleanup in case of errors. Yes, a failed mmap() will always eventually clean up any partial mappings, but without any explicit lifetime in the page table mapping itself, it's very easy to do the error handling in the wrong order. In particular, it's easy to mistakenly free the physical backing store before the page tables are actually cleaned up and (temporarily) have stale dangling PTE entries. To make this situation less error-prone, just make sure that any partial pfn mapping is torn down early, before any other error handling.

Gravité et risque d'exploitation

CVE-2024-47674 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.25 %, ce qui la place devant 14.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959, <65d0db500d7c07f0f76fc24a4d837791c4862cd2, <5.13, 6.6.52, 69d4e1ce9087c8767f2fe9b9426fa2755c8e9072, 0, <35770ca6180caa24a2b258c99a87bd437a1ee10f, <a95a24fcaee1b892e47d5e6dcc403f713874ee80, <=6.6.*, <79a61cc3fc0466ad2b7b89618a6157785f0293b3, 6.1.111, 5.13, <954fd4c81f22c4b6ba65379a81fd252971bf4ef3, 6.10.11, 6.11, <=*, b97a50adb37e98b940a30c4656565ff609aa8f94, <=5.15.*, <3213fdcab961026203dd587a4533600c70b3336b, 5.15.168, 74ffa5a3e68504dd289135b1cf0422c19ffb3f2e, <=6.10.*) 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