Skip to main content
VulnerabilityPublished

CVE-2026-99668: Linux kernel · mm/huge_memory: fix zapping migration entries for device-private THPs

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 63a940541358d09cc9f02d40b71eb8d3917a21c0 or 2d7e94a16d0d33ce2cce5ea06cf61079c392d351 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 63a940541358d09cc9f02d40b71eb8d3917a21c0, 2d7e94a16d0d33ce2cce5ea06cf61079c392d351

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 63a940541358d09cc9f02d40b71eb8d3917a21c0 or 2d7e94a16d0d33ce2cce5ea06cf61079c392d351.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 368076f52ebeecd33e10a9f80905d7508b6b6149, < 63a940541358d09cc9f02d40b71eb8d3917a21c0
Fixed in
  • 63a940541358d09cc9f02d40b71eb8d3917a21c0
LinuxLinuxAffected
  • ≥ 368076f52ebeecd33e10a9f80905d7508b6b6149, < 2d7e94a16d0d33ce2cce5ea06cf61079c392d351
Fixed in
  • 2d7e94a16d0d33ce2cce5ea06cf61079c392d351
LinuxLinuxAffected
  • =6.19
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: fix zapping migration entries for device-private THPs A PMD migration entry can refer to a device-private folio. zap_huge_pmd_folio() checks the folio type instead of the entry type, so it treats such a migration entry as a device-private entry. Installing the migration entry already removed the reverse mapping and dropped the mapping reference. Zapping it must not repeat those operations. Concurrent MADV_DONTNEED during migration back to system memory can trigger this. Check the PMD entry type using pmd_is_device_private_entry(). Fix generated by an LLM and sent by Chris Mason in private. [ david: simplify description ]

References

Community reviews

Loading reviews…