CVE-2026-74354: bpf: Take mmap_lock in zap_pages()
In the Linux kernel, the following vulnerability has been resolved:
bpf: Take mmaplock in zappages()
zapvmarange() requires the owning mm's mmaplock to be held.
Taking mmapreadlock under arena->lock would AB-BA against arenavmclose() and arenamapmmap(), both of which run with mmapwritelock held and then acquire arena->lock. Instead drop arena->lock, mmgetnotzero() the vma's mm, take mmapreadlock, and re-resolve the vma via findvma() since it may have been unmapped or replaced while waiting.
Track processed vmls with a per-call generation in vml->zapgen and serialize zappages() callers with a new arena->zapmutex so concurrent callers on different uaddr ranges do not mark each other's vmls processed before the zap is done.
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
Event History
Frequently Asked Questions
What is the severity of CVE-2026-74354?
CVE-2026-74354 has a risk score of 34, indicating it poses a moderate threat.
How do I fix CVE-2026-74354?
Fixes for CVE-2026-74354 are included in the Linux kernel updates released after August 15, 2026.
What systems are affected by CVE-2026-74354?
CVE-2026-74354 affects specific versions of the Linux kernel where mmap_lock handling is not properly implemented.
What does CVE-2026-74354 impact?
CVE-2026-74354 affects the memory management and could lead to potential race conditions in the kernel.
Is CVE-2026-74354 actively being exploited?
As of now, there are no reports indicating active exploitation of CVE-2026-74354 in the wild.