drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8a6e85f75a83d16a71077e41f2720c691f432002 · < 3d6586008f7b638f91f3332602592caa8b00b559| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ACRN RAM mapping code does not adequately check PTE permissions, reject refcounted pages, or validate every PTE in a mapping range. An affected mapping can result in use-after-free or access to unintended PFNs. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the ACRN driver should check their exposure; affected versions are not specified.