PoC Monitor
← All CVEs
CVE-2026-89760published 11 Sep 2026 19:47 UTCData: JSON · API

Linux

mm, swap: don't free a hibernation slot that is in the swap cache

In the Linux kernel, the following vulnerability has been resolved: mm, swap: don't free a hibernation slot that is in the swap cache A slot with a folio in the swap cache is freed when the folio leaves the cache, not when its count drops. swap_put_entries_cluster() follows that rule. swap_free_hibernation_slot() does not, it calls __swap_cluster_free_entries() whether or not a folio sits on the slot. Cluster readahead can put one there. It walks a raw page_cluster sized window of offsets around the faulting entry, and a hibernation slot passes __swap_cache_add_check() because it is not a folio and its count is not zero. Freeing the slot then clears the entry under that folio. The folio is now unreachable from the swap table, and the offset goes back to the allocator. The folio is still on the LRU though, so reclaim can pick it up later. It then takes the old offset out of folio->swap and overwrites the table entry there, which by then may belong to someone else. This bug can trigger silent memory corruption, process crashes, or data instability across completely unrelated userspace applications - typically occurring when uswsusp is preparing the hibernation image. I found this while working on giving hibernation slots their own marker in the swap table, which I had discussed with Kairui. (https://lore.kernel.org/linux-mm/abp7aDgYLrxF3Me8@KASONG-MC4/) As far as I know there are no reports, so there is no Reported-by/Closes to add. Check for a cached folio before freeing. The slot is then left in the ordinary state where only the swap cache holds it, and it is freed when the folio leaves the cache, either through the reclaim below or through normal reclaim later.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 0d6af9bcf383bcdf601e670bb605861b01e318e7, < a6df73156f2d85746c69adbf13d0f5ea200e0626
  • >= 0d6af9bcf383bcdf601e670bb605861b01e318e7, < 10d9012e83efedde8718ceaa5053f836e0c8596c

Fixed in a6df73156f2d85746c69adbf13d0f5ea200e0626, 10d9012e83efedde8718ceaa5053f836e0c8596c

Linux Linux
  • 7.1

Fixed in 0, 7.2.4, 7.3

Mitigation

Upgrade Linux to a6df73156f2d85746c69adbf13d0f5ea200e0626 or 10d9012e83efedde8718ceaa5053f836e0c8596c or later.

Upgrade Linux to 0 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.