fs/proc/task_mmu: pin mm_users in do_pagemap_scan()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel abc9c0f4f850d23e55f4230cd0f54938a64267bf, Kernel 14a853bf3e6f0dd62ff479a36613411237dec24c, Kernel 4fb975471717c953f912776bb60301add1ffae11 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: fs/proc/task_mmu: pin mm_users in do_pagemap_scan() The PAGEMAP_SCAN ioctl takes mmap_read_lock() on an mm obtained from /proc/<pid>/pagemap without holding a reference to mm_users. proc_mem_open() deliberately grabs only mm_count, so a consumer that touches the address space has to call mmget_not_zero() first. Every other consumer in this file does -- m_start(), do_procmap_query(), show_smaps_rollup() and pagemap_read() -- but do_pagemap_scan() does not. Without that reference the target can reach exit_mmap() concurrently, and exit_mmap() calls unmap_vmas() while holding mmap_lock only for reading, which does not exclude the scanner. For ordinary VMAs this is harmless, as free_pgtables() and remove_vma() run afterwards under mmap_write_lock. A shared hugetlb VMA is different: __hugetlb_zap_end() frees the VMA's hugetlb_vma_lock inside the read-locked phase. walk_hugetlb_range() can therefore load vma->vm_private_data, have the lock freed underneath it, and then down_read() a freed rw_semaphore. The load happens before the freeing side clears the pointer, so this is a use-after-free and not a NULL dereference. Any unprivileged user can reach it with no huge pages configured, as hugetlb_reserve_pages() allocates the lock before the VM_NORESERVE early return. Pin mm_users across the scan, the way the other consumers do. mmput() from the exiting task can then no longer reach exit_mmap() while a walk is in progress. [akpm@linux-foundation.org: remove unneeded & undesirable test for !mm]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=52526ca7fdb905a768a93f8faa418e9b988fc34b <abc9c0f4f850d23e55f4230cd0f54938a64267bf, >=52526ca7fdb905a768a93f8faa418e9b988fc34b <14a853bf3e6f0dd62ff479a36613411237dec24c, >=52526ca7fdb905a768a93f8faa418e9b988fc34b <4fb975471717c953f912776bb60301add1ffae11, >=52526ca7fdb905a768a93f8faa418e9b988fc34b <6e2299a9356de3364e193d6eaf123b90d7698c1d, =6.7 | abc9c0f4f850d23e55f4230cd0f54938a64267bf, 14a853bf3e6f0dd62ff479a36613411237dec24c, 4fb975471717c953f912776bb60301add1ffae11, 6e2299a9356de3364e193d6eaf123b90d7698c1d |
| linux-kernel: Kernel | >=6.19.0 <7.3.2, >=6.7.0 <6.12.117, >=6.13.0 <6.18.61 | 7.3.2, 6.12.117, 6.18.61 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket