CVE-2026-74420: drm/gpusvm: Reject VMAs with VM_IO or VM_PFNMAP when creating SVM ranges
In the Linux kernel, the following vulnerability has been resolved:
drm/gpusvm: Reject VMAs with VMIO or VMPFNMAP when creating SVM ranges
VMAs marked with VMIO or VMPFNMAP are not backed by struct page objects, which GPUSVM requires in order to operate correctly. In particular, getpages() relies on hmmrangefault() to resolve struct pages for the target range.
Attempting to create an SVM range on such VMAs results in repeated getpages() failures and can lead to an infinite loop inside a driver’s page‑fault handler. Prevent this by rejecting ranges on VMIO or VMPFNMAP VMAs and returning -EIO.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38~24.04.4 - Upgrade
Upgrade
ubuntu/linux-nvidia-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1024.25~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-38.38 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-nvidia-bosto a version that resolves this vulnerability.Fixed in 7.0.0-2022.23 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Compensating control
When creating GPUSVM SVM ranges, reject VMAs marked with VM_IO or VM_PFNMAP and return -EIO.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-74420?
CVE-2026-74420 has a risk score of 23.
How do I fix CVE-2026-74420?
To fix CVE-2026-74420, update your Linux kernel to the latest version that addresses this vulnerability.
What does CVE-2026-74420 affect in the Linux kernel?
CVE-2026-74420 affects the handling of VMAs marked with VM_IO or VM_PFNMAP in the context of GPUSVM.
Is CVE-2026-74420 a critical vulnerability?
CVE-2026-74420 is considered to have a significant risk, so it should be addressed promptly.
When was CVE-2026-74420 published?
CVE-2026-74420 was published on August 15, 2026.