cbcvebase.
CVE-2024-38610
published 2024-06-19

CVE-2024-38610: 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…

PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.21%
11.7th percentile
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.

Affected

24 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.94-1 (bookworm)linux 6.1.94-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux
linuxlinux>= 5.15.33 < 5.15.1615.15.161
linuxlinux>= 5.16.19 < 5.175.17
linuxlinux>= 5.17.2 < 5.185.18
linuxlinux>= 8a6e85f75a83d16a71077e41f2720c691f432002 < afeb0e69627695f759fc73c39c1640dbf8649b32afeb0e69627695f759fc73c39c1640dbf8649b32
linuxlinux>= 8a6e85f75a83d16a71077e41f2720c691f432002 < e873f36ec890bece26ecce850e969917bceebbb6e873f36ec890bece26ecce850e969917bceebbb6
linuxlinux>= 8a6e85f75a83d16a71077e41f2720c691f432002 < 4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b44c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4
linuxlinux>= 8a6e85f75a83d16a71077e41f2720c691f432002 < 2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb
linuxlinux>= 8a6e85f75a83d16a71077e41f2720c691f432002 < 3d6586008f7b638f91f3332602592caa8b00b5593d6586008f7b638f91f3332602592caa8b00b559
linuxlinux>= b9c43aa0b18da5619aac347d54cb67fe30d1f884 < 5c6705aa47b5b78d7ad36fea832bb69caa5bf49a5c6705aa47b5b78d7ad36fea832bb69caa5bf49a
linuxlinux_kernel>= 0 < 6.1.94-16.1.94-1
linuxlinux_kernel>= 0 < 6.8.12-16.8.12-1
linuxlinux_kernel>= 0 < 6.8.12-16.8.12-1
linuxlinux_kernel>= 0 < 5.15.0-121.1315.15.0-121.131
linuxlinux_kernel>= 0 < 6.8.0-40.406.8.0-40.40
linuxlinux_kernel>= 5.15.33 < 5.15.1615.15.161
linuxlinux_kernel>= 5.16.19 < 5.175.17
linuxlinux_kernel>= 5.17.2 < 6.1.936.1.93
linuxlinux_kernel>= 6.2 < 6.6.336.6.33
linuxlinux_kernel>= 6.7 < 6.8.126.8.12
linuxlinux_kernel>= 6.9 < 6.9.36.9.3

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
vendor_ubuntu6.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.