{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "867a43a34ff8a38772212045262b2c9b77807ea3"
            },
            {
              "fixed": "3627d4eaa7f4426b979d497544ce23cb8884134b"
            },
            {
              "fixed": "d03df42ddae196f20e9cfb775704e60269eb6b44"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.9.0"
            },
            {
              "fixed": "7.3.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99652.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: fix deadlock of mremap() against UFFDIO_MOVE\n\nWith per-VMA locks, UFFDIO_MOVE can run concurrently with mremap()\non different VMAs in the same mm. Those VMAs can share page tables, so\nboth operations can acquire the same pair of page-table locks.\n\nUFFDIO_MOVE orders the locks by address, while mremap() takes the source\nlock first. These conflicting orders can deadlock; mremap() holding\nmmap_lock for writing no longer helps.\n\nMove double_pt_lock() and double_pt_unlock() to mm/internal.h and use\nthem for all page-table moves in mremap(). Preserve the source entry\nchecks after acquiring both locks. Remove the comments claiming that\nexclusive mmap_lock makes lock ordering irrelevant.\n\nIn move_ptes(), make sure to just recheck source and destination PMD\nafter taking the locks and drop the overly-long comment.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\n[ david: use new helpers consistently; simplify description and comments;\n         move_ptes() fixup ]",
  "id": "CVE-2026-99652",
  "modified": "2026-11-20T06:45:23.799716389Z",
  "published": "2026-11-20T05:50:05.321Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3627d4eaa7f4426b979d497544ce23cb8884134b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d03df42ddae196f20e9cfb775704e60269eb6b44"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99652.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99652"
    }
  ],
  "schema_version": "1.9.2",
  "summary": "mm: fix deadlock of mremap() against UFFDIO_MOVE"
}