CVE-2026-89760

Description

A flaw was found in the Linux kernel's memory management (mm) and swap subsystem. This vulnerability occurs when the swap_free_hibernation_slot() function incorrectly frees a hibernation slot while a memory page (folio) is still present in the swap cache. This can lead to silent memory corruption, process crashes, or data instability across unrelated user applications, typically during the preparation of a hibernation image by uswsusp.

Statement

A moderate impact flaw was found in the Linux kernel's memory management (mm) and swap subsystem. The swap_free_hibernation_slot() function incorrectly frees a hibernation swap slot while a folio is still present in the swap cache. This can occur after swap cluster readahead places a folio on the slot, because a hibernation slot passes the __swap_cache_add_check() test. Once the slot is freed, its offset is returned to the swap allocator while the folio remains on the LRU list; when memory reclaim later writes that folio back out using its stale folio->swap offset, it can overwrite a swap table entry that has by then been reallocated to another user. The result can be silent memory corruption, process crashes, or data instability across completely unrelated applications, typically triggered while uswsusp prepares the hibernation image. Exploitation requires local access and depends on specific timing and memory state conditions, so Red Hat rates this flaw moderate impact (CVSS 3.1 score of 7.0, CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), lower than the upstream CVEORG score of 7.8 primarily due to the higher attack complexity. Red Hat Enterprise Linux 6 is out of support scope, and the Red Hat Enterprise Linux 7, 8, 9, and 10 kernels do not contain the vulnerable code and are therefore not affected. Red Hat OpenShift Container Platform 4 RHEL CoreOS builds are likewise not affected. Red Hat OpenShift Container Platform 5.0 and 5.1 (RHEL CoreOS 9) are affected; the fix on those streams is currently deferred, so systems using swap and hibernation there remain at residual risk of memory corruption, although practical exposure is limited because triggering the flaw requires the specific race between hibernation slot freeing and swap cluster readahead on a hibernating system.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.