Skip to main content
VulnerabilityPublished

CVE-2026-99652: Linux kernel · mm: fix deadlock of mremap() against UFFDIO_MOVE

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to d03df42ddae196f20e9cfb775704e60269eb6b44 or 3627d4eaa7f4426b979d497544ce23cb8884134b when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d03df42ddae196f20e9cfb775704e60269eb6b44, 3627d4eaa7f4426b979d497544ce23cb8884134b

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to d03df42ddae196f20e9cfb775704e60269eb6b44 or 3627d4eaa7f4426b979d497544ce23cb8884134b.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < d03df42ddae196f20e9cfb775704e60269eb6b44
Fixed in
  • d03df42ddae196f20e9cfb775704e60269eb6b44
LinuxLinuxAffected
  • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < 3627d4eaa7f4426b979d497544ce23cb8884134b
Fixed in
  • 3627d4eaa7f4426b979d497544ce23cb8884134b
LinuxLinuxAffected
  • =6.9
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm: fix deadlock of mremap() against UFFDIO_MOVE With per-VMA locks, UFFDIO_MOVE 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. UFFDIO_MOVE orders the locks by address, while mremap() takes the source lock first. These conflicting orders can deadlock; mremap() holding mmap_lock for writing no longer helps. Move double_pt_lock() and double_pt_unlock() 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 mmap_lock makes lock ordering irrelevant. In move_ptes(), 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; move_ptes() fixup ]

References

Community reviews

Loading reviews…