CVE-2026-90303

Unknown

Last modified

CVE-2026-90303 is a vulnerability of currently unknown severity. 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..

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 6d021b724481fbb908eb29384898deb9f00dfe70, < ab14f07952adfe735d86a53518f8cd576dfd5892; >= 6d021b724481fbb908eb29384898deb9f00dfe70, < 07e4d5380f2a844ab7a1b440dde350caf561cbb0; >= 6d021b724481fbb908eb29384898deb9f00dfe70, < 2a14d7797a49a47bccd1a9327fd69da838dcb0dd; >= 6d021b724481fbb908eb29384898deb9f00dfe70, < 63e3c958a602d0896a101a897c2361878c266ca7; >= 6d021b724481fbb908eb29384898deb9f00dfe70, < 59bbf86d0ff9373bfa033ca123c1e924f09f1eba; >= 6d021b724481fbb908eb29384898deb9f00dfe70, < c71f9a56520b419e55d173052629f2324deb5549; >= 6d021b724481fbb908eb29384898deb9f00dfe70, < 720408d98d9fb3c91a12090436734c8c61f04545; >= 6d021b724481fbb908eb29384898deb9f00dfe70, < 1039bffd6ae9c75b42b7d148d6c1106134107b66
LinuxLinux4.0

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-90303?
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.
How severe is CVE-2026-90303?
Severity scoring for CVE-2026-90303 is pending analysis.
How do I fix CVE-2026-90303?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-90303?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST