Skip to main content
VulnerabilityPublished

CVE-2026-99729: Linux kernel · mm/rmap: handle device-exclusive entries in folio_referenced_one()

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99729· Medium

Not known to be exploited : upgrade to f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c or 9075e5fbad71e00a73cddef901a2a08ad7b51af5 when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c, 9075e5fbad71e00a73cddef901a2a08ad7b51af5

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 f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c or 9075e5fbad71e00a73cddef901a2a08ad7b51af5.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b756a3b5e7ead8f6f4b03cea8ac22478ce04c8a8, < f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c
Fixed in
  • f3c493d2f42b5f44a5c134d8d7ea7f960caf5e2c
LinuxLinuxAffected
  • ≥ b756a3b5e7ead8f6f4b03cea8ac22478ce04c8a8, < 9075e5fbad71e00a73cddef901a2a08ad7b51af5
Fixed in
  • 9075e5fbad71e00a73cddef901a2a08ad7b51af5
LinuxLinuxAffected
  • =5.14
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/rmap: handle device-exclusive entries in folio_referenced_one() page_vma_mapped_walk() can return non-present device-exclusive entries, but folio_referenced_one() passes them to PTE young-bit accessors that require present PTEs. We must neither call clear_flush_young_ptes_notify() nor folio_pte_batch() with non-present entries. For example, clearing the young bit on non-present PTEs can corrupt the entry: on arm64 PTE_AF overlaps the swap type, so clearing it turns a device-exclusive entry into an ordinary swap entry. folio_pte_batch() will VM_WARN_ON_FOLIO. Apply the same approach as the previous fixes to e.g., damon_ptep_mkold(): treat these entries as old from the CPU's perspective and obtain their young state through the MMU notifier. Skip PTE batching and MGLRU look-around for non-present entries, and don't modify non-present PTEs.

References

Community reviews

Loading reviews…