CVE-2026-90303

ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults

N/A
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults When CONFIG_DEBUG_USER=y, and cmdline "user_debug=31" is set, a user fault may trigger show_pte() without any lock. If another thread in the same process concurrently calls munmap(), the page table pages may be freed while show_pte() is still traversing them, causing a use-after-free in show_pte(). If CONFIG_ARM_LPAE=y, this may cause a kernel panic if the pages table of PMD are freed when show_pte() is running. Acquire mmap_write_lock() around show_pte() for user faults to fix the contention. For user faults, additionally restrict that show_pte() is called only when the addr is a user-space address (addr < TASK_SIZE). This is because the lock of tsk->mm only protects the virtual memory of user address space, furthermore, dumping the page tables of a kernel-space address for user faults is unnecessary and may have security implications. Keep everything unchanged for kernel faults, because the kernel is already in the "oops" state, acquiring a lock may risk a deadlock.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.06d021b724481fbb908eb29384898deb9f00dfe70
Vendor states this is fixed in 07e4d5380f2a844ab7a1b440dde350caf561cbb0 (fixed)
Vendor states this is fixed in 1039bffd6ae9c75b42b7d148d6c1106134107b66 (fixed)
Vendor states this is fixed in 2a14d7797a49a47bccd1a9327fd69da838dcb0dd (fixed)
Vendor states this is fixed in 59bbf86d0ff9373bfa033ca123c1e924f09f1eba (fixed)
Vendor states this is fixed in 63e3c958a602d0896a101a897c2361878c266ca7 (fixed)
Vendor states this is fixed in 720408d98d9fb3c91a12090436734c8c61f04545 (fixed)
Vendor states this is fixed in ab14f07952adfe735d86a53518f8cd576dfd5892 (fixed)
Vendor states this is fixed in c71f9a56520b419e55d173052629f2324deb5549 (fixed)
Vendor states this is fixed in 4.0 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card