CVE-2026-89760
Received Received - Intake

Memory Corruption in Linux Kernel Hibernation

Vulnerability report for CVE-2026-89760, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-11

Last updated on: 2026-09-11

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-11
Generated
2026-09-12
AI Q&A
2026-09-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves incorrect handling of hibernation slots in the swap cache. A slot with a folio in the swap cache is freed when the folio leaves the cache, but swap_free_hibernation_slot() does not follow this rule. It may free a slot even if a folio is still present, leading to memory corruption or crashes during hibernation preparation.

Detection Guidance

This vulnerability is specific to the Linux kernel's memory management and hibernation functionality. Detection requires checking kernel logs for hibernation-related errors or memory corruption events. Monitor system logs for crashes or unusual behavior during hibernation attempts. No direct commands are provided in the context, but examining kernel logs with 'dmesg' or 'journalctl -k' may reveal issues.

Impact Analysis

This bug can cause silent memory corruption, process crashes, or data instability in unrelated applications. It typically occurs when uswsusp prepares a hibernation image, potentially affecting system stability and reliability.

Mitigation Strategies

Apply the latest Linux kernel patches that address this issue. Disable hibernation (uswsusp) if not required, as the vulnerability is triggered during hibernation image preparation. Monitor system stability and kernel logs for signs of memory corruption or crashes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-89760. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart