drm/shmem_helper: Check VMA boundaries for PMD mappings
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/shmem_helper: Check VMA boundaries for PMD mappings
In the ->huge_fault handler do not install a PMD huge page mapping if the huge page exceeds the boundaries of the VMA.
All other ->huge_fault handlers have similar checks and the resulting mapping will trigger a VM_BUG_ON_VMA() if it ever reaches copy_pmd_range().
From the CVE record · Linux
The Linux kernel’s drm/shmem_helper huge-page fault handler can install a PMD mapping that extends beyond the boundaries of a virtual memory area (VMA). If that mapping reaches copy_pmd_range(), it triggers a kernel VM_BUG_ON_VMA() check. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel should check whether their kernel includes the affected drm/shmem_helper code; affected versions are not specified.