CVE Feed
— Unscored

In the Linux kernel, the following vulnerability has been resolved: mm: fix deadlock of mremap() against UFFDIOMOVE With per-VMA locks,…

CVE-2026-99652

In the Linux kernel, the following vulnerability has been resolved: mm: fix deadlock of mremap() against UFFDIOMOVE With per-VMA locks, UFFDIOMOVE can run concurrently with mremap() on different VMAs in the same mm. Those VMAs can share page tables, so both operations can acquire the same pair of page-table locks. UFFDIOMOVE orders the locks by address, while mremap() takes the source lock first. These conflicting orders can deadlock; mremap() holding mmaplock for writing no longer helps. Move doubleptlock() and doubleptunlock() to mm/internal.h and use them for all page-table moves in mremap(). Preserve the source entry checks after acquiring both locks. Remove the comments claiming that exclusive mmaplock makes lock ordering irrelevant. In moveptes(), make sure to just recheck source and destination PMD after taking the locks and drop the overly-long comment. Fix generated by an LLM and sent by Chris Mason in private. [ david: use new helpers consistently; simplify description and comments; moveptes() fixup ]

Assessment

CVSS
Not yet scored
Severity
Unscored
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
20 November 2026
Last updated
20 November 2026
Affected
Linux · Linux
Assigner
Linux

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99652