cve.bz

CVE-2026-89757 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: mm/mglru: fix and remove redundant unevictable folio handling sort_folio() has a shortcut for moving folios that are no longer evictable but are still sitting on a generation list. However, this shortcut is buggy. It does not follow the PG_lru usage convention, and it has a more serious issue. Unevictable folios are not threaded on lists[LRU_UNEVICTABLE], so that folio->lru can be reused to hold folio->mlock_count (see the comment in lruvec_init()). Hence lruvec_add_folio() skips the list_add() for them, and every other place that turns a folio unevictable initialises mlock_count explicitly: lru_add() sets it to 0, __mlock_folio() and __mlock_new_folio() set it to !!folio_test_mlocked(folio). sort_folio() sets nothing, and the lru_gen_del_folio() right above it may have already poisoned folio->lru via list_del(), so mlock_count ends up aliasing LIST_POISON2, which reads as 0x122, i.e. 290. The result is user visible. On munlock, __munlock_folio() decrements that bogus count, finds it still non-zero and bails out before clearing PG_mlocked, so the folio remains unevictable and the Mlocked accounting stays inflated until the folio is freed. The shortcut also touches the LRU flags in the wrong order. It calls lru_gen_del_folio() while PG_lru is still set, so a concurrent folio_test_clear_lru() (e.g. compaction, folio_isolate_lru()) can succeed on a folio that has already been taken off the generation list, which may lead to unexpected behavior. So fix it by isolating them as common folios and letting the generic shrink path cull them. This matches the classical LRU behavior, and there should be no visible effect on the generic eviction or isolation behavior. There is no performance concern either, such a folio goes through this once, and then it is off the generation lists for good.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.114
  • Linux Linux: fixed in 6.18.51
  • Linux Linux: fixed in 7.2.4
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-89757 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89757?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89757?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-89757 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.1 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.160
Linux6.126.12.114
Linux6.186.18.51
Linux7.27.2.4
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-89757
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-89757
Debian13linux6.12.115-2DEBIAN-CVE-2026-89757
Debian14linux7.2.6-1DEBIAN-CVE-2026-89757
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89757
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89757
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89757
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-89757
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 44 moreno fix listedUBUNTU-CVE-2026-89757
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-89757 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-89757 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-89757 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-89757 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-89757 USN-9020-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-89757
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-89757 USN-8959-1
15 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.41.1SUSE-SU-2026:24651-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.41.1SUSE-SU-2026:24662-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.41.1.160000.2.32SUSE-SU-2026:24662-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.41.1.160000.2.32SUSE-SU-2026:24643-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.41.1SUSE-SU-2026:24643-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.41.1SUSE-SU-2026:24648-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.41.1.160000.2.31openSUSE-SU-2026:22266-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.41.1openSUSE-SU-2026:22266-1
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Azure Linux3kernel6.6.161.1-1AZL-100605
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-89757
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-89757
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-89757

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity flaw was found in the Linux kernel's multi-generational LRU (MGLRU) memory management subsystem. The shortcut in sort_folio() that moves folios which are no longer evictable off an MGLRU generation list fails to initialise folio->mlock_count, allowing that field to alias the list poison value left behind by list_del(). When such a folio is subsequently munlocked, __munlock_folio() decrements the bogus count, finds it still non-zero, and returns before clearing PG_mlocked, so the folio remains unevictable and the Mlocked accounting stays inflated until the folio is freed. The shortcut also touches the LRU flags in the wrong order, calling lru_gen_del_folio() while PG_lru is still set, which can allow a concurrent folio_test_clear_lru() (for example during compaction or folio isolation) to succeed on a folio already removed from the generation list and lead to unexpected behavior. A local unprivileged user can trigger this through ordinary mlock/munlock activity on memory managed by MGLRU; the result is inflated memory accounting and memory pages that remain locked in memory, which can contribute to memory resource exhaustion and reduced system stability. Red Hat classifies this flaw as MODERATE impact with a CVSS 3.1 base score of 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), affecting only availability.

Red Hat Enterprise Linux 9 (kernel and kernel-rt, from the 9.4 update stream onward) and Red Hat Enterprise Linux 10, as well as Red Hat OpenShift Container Platform 4.16 and later (including 5.0 and 5.1) and Red Hat In-Vehicle OS 2.x, are affected. Because the issue is of moderate severity with a CVSS score below 7.0, the fix is deferred and no updates are currently planned for these products; the residual risk is that unevictable memory can accumulate with inflated accounting on affected systems until the corresponding folios are freed. Red Hat Enterprise Linux 7 and 8, the Red Hat Enterprise Linux 9.2 update stream, and Red Hat OpenShift Container Platform 4.12 through 4.15 are not affected because the vulnerable code is not present in the kernel versions shipped in those products.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-89757.

References

Check your stackJSON