Skip to main content
VulnerabilityPublished

CVE-2026-99656: Linux kernel · mm/madvise: fix data loss from MADV_FREE on a KSM page

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99656· High

Not known to be exploited · fixed in af2feafb0437fab5ed9d02eeb1c06ef66e05c55a : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in af2feafb0437fab5ed9d02eeb1c06ef66e05c55a, 64f273b71bf714dd22b803a87d65bb40faaffcad, 22d043c1da48d6c7274f9dd900714b6d58b7b9c6 +1

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 af2feafb0437fab5ed9d02eeb1c06ef66e05c55a, 64f273b71bf714dd22b803a87d65bb40faaffcad, 22d043c1da48d6c7274f9dd900714b6d58b7b9c6 or 8b6860f17b4de23a0b19045c066dc0679e50f0ba.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9, < af2feafb0437fab5ed9d02eeb1c06ef66e05c55a
Fixed in
  • af2feafb0437fab5ed9d02eeb1c06ef66e05c55a
LinuxLinuxAffected
  • ≥ 854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9, < 64f273b71bf714dd22b803a87d65bb40faaffcad
Fixed in
  • 64f273b71bf714dd22b803a87d65bb40faaffcad
LinuxLinuxAffected
  • ≥ 854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9, < 22d043c1da48d6c7274f9dd900714b6d58b7b9c6
Fixed in
  • 22d043c1da48d6c7274f9dd900714b6d58b7b9c6
LinuxLinuxAffected
  • ≥ 854e9ed09dedf0c19ac8640e91bcc74bc3f9e5c9, < 8b6860f17b4de23a0b19045c066dc0679e50f0ba
Fixed in
  • 8b6860f17b4de23a0b19045c066dc0679e50f0ba
LinuxLinuxAffected
  • =4.5
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/madvise: fix data loss from MADV_FREE on a KSM page MADV_FREE can clear the dirty flag of a singly mapped KSM folio. The folio remains in the stable tree and can gain new mappings without being dirtied again. Once marked lazyfree, reclaim can discard data that those mappings still need. KSM always marks a folio dirty when converting it to a KSM folio in try_to_merge_one_page(). Marking a folio lazyfree clears PG_swapbacked but leaves PG_dirty unchanged. Preserving PG_dirty makes reclaim restore PG_swapbacked instead of discarding the folio. This also protects folios that were already lazyfree when KSM converted them. Skip KSM folios before clearing their dirty flag, checking under the folio lock to serialize with KSM conversion.

References

Community reviews

Loading reviews…