CVE-2024-38610
Vulnérabilité élevée dans Linux (Linux)
Description
In the Linux kernel, the following vulnerability has been resolved: drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map() Patch series "mm: follow_pte() improvements and acrn follow_pte() fixes". Patch #1 fixes a bunch of issues I spotted in the acrn driver. It compiles, that's all I know. I'll appreciate some review and testing from acrn folks. Patch #2+#3 improve follow_pte(), passing a VMA instead of the MM, adding more sanity checks, and improving the documentation. Gave it a quick test on x86-64 using VM_PAT that ends up using follow_pte(). This patch (of 3): We currently miss handling various cases, resulting in a dangerous follow_pte() (previously follow_pfn()) usage. (1) We're not checking PTE write permissions. Maybe we should simply always require pte_write() like we do for pin_user_pages_fast(FOLL_WRITE)? Hard to tell, so let's check for ACRN_MEM_ACCESS_WRITE for now. (2) We're not rejecting refcounted pages. As we are not using MMU notifiers, messing with refcounted pages is dangerous and can result in use-after-free. Let's make sure to reject them. (3) We are only looking at the first PTE of a bigger range. We only lookup a single PTE, but memmap->len may span a larger area. Let's loop over all involved PTEs and make sure the PFN range is actually contiguous. Reject everything else: it couldn't have worked either way, and rather made use access PFNs we shouldn't be accessing.
Gravité et risque d'exploitation
CVE-2024-38610 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 10.9 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions 5.15.33, <=6.1.*, 5.18, 6.10, 0, <e873f36ec890bece26ecce850e969917bceebbb6, <5.17, <5.18, <=6.6.*, 6.8.12, <=6.9.*, <2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb, <3d6586008f7b638f91f3332602592caa8b00b559, <5c6705aa47b5b78d7ad36fea832bb69caa5bf49a, 6.6.33, 5.15.161, 5.16.19, <5.15.161, <=6.8.*, <4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4, 6.1.93, 5.17.2, <=*, <=5.15.*, 8a6e85f75a83d16a71077e41f2720c691f432002, b9c43aa0b18da5619aac347d54cb67fe30d1f884, 02098ac42b7ff055ec72cd083ee1eb0a23481a19, 149d5fb7e0124c3763e92edd1fde19417f4d2d09, 6.9.3, <afeb0e69627695f759fc73c39c1640dbf8649b32) 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
- https://git.kernel.org/stable/c/5c6705aa47b5b78d7ad36fea832bb69caa5bf49a
- https://git.kernel.org/stable/c/afeb0e69627695f759fc73c39c1640dbf8649b32
- https://git.kernel.org/stable/c/e873f36ec890bece26ecce850e969917bceebbb6
- https://git.kernel.org/stable/c/4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4
- https://git.kernel.org/stable/c/2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb
- https://git.kernel.org/stable/c/3d6586008f7b638f91f3332602592caa8b00b559
