CVE-2026-99477
fs/proc/task_mmu: pin mm_users in do_pagemap_scan()
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. [[email protected]: remove unneeded & undesirable test for !mm]
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 52526ca7fdb905a768a93f8faa418e9b988fc34b; < 6e2299a9356de3364e193d6eaf123b90d7698c1d (affected, git) ≥ 52526ca7fdb905a768a93f8faa418e9b988fc34b; < abc9c0f4f850d23e55f4230cd0f54938a64267bf (affected, git) ≥ 52526ca7fdb905a768a93f8faa418e9b988fc34b; < 14a853bf3e6f0dd62ff479a36613411237dec24c (affected, git) ≥ 52526ca7fdb905a768a93f8faa418e9b988fc34b; < 4fb975471717c953f912776bb60301add1ffae11 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
6.7 (affected) ≥ 0; < 6.7 (unaffected, semver) ≥ 6.12.117; ≤ 6.12.* (unaffected, semver) ≥ 6.18.61; ≤ 6.18.* (unaffected, semver) ≥ 7.3.2; ≤ 7.3.* (unaffected, semver) ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA: Linux |
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/6e2299a9356de3364e193d6eaf123b90d7698c1dCNA: Linux
- https://git.kernel.org/stable/c/abc9c0f4f850d23e55f4230cd0f54938a64267bfCNA: Linux
- https://git.kernel.org/stable/c/14a853bf3e6f0dd62ff479a36613411237dec24cCNA: Linux
- https://git.kernel.org/stable/c/4fb975471717c953f912776bb60301add1ffae11CNA: Linux
- https://git.kernel.org/stable/c/14a853bf3e6f0dd62ff479a36613411237dec24c416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/4fb975471717c953f912776bb60301add1ffae11416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/6e2299a9356de3364e193d6eaf123b90d7698c1d416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/abc9c0f4f850d23e55f4230cd0f54938a64267bf416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.