CVE-2026-89757

published 11 Sep 2026 · updated 14 Nov 2026

mm/mglru: fix and remove redundant unevictable folio handling

3.6LowCVSS 3.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f7e698e326b239a91ea15844817551921209e826, Kernel 15d3a2a71c8bf7333d019d249ee33669e69e4275, Kernel 49193dac48d30eee2a21da88a7262d52a7feefae and 8 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=ac35a490237446b71e3b4b782b1596967edd0aa8 <f7e698e326b239a91ea15844817551921209e826, >=ac35a490237446b71e3b4b782b1596967edd0aa8 <15d3a2a71c8bf7333d019d249ee33669e69e4275, >=ac35a490237446b71e3b4b782b1596967edd0aa8 <49193dac48d30eee2a21da88a7262d52a7feefae, >=ac35a490237446b71e3b4b782b1596967edd0aa8 <54a58d6656dd403b686b247f0bad8507cbfb45df, >=ac35a490237446b71e3b4b782b1596967edd0aa8 <b1d7c69e6c7d3ec47513b911ce7529e56d183dad, >=ac35a490237446b71e3b4b782b1596967edd0aa8 <e9f2160081a1e3ebb285bd71be3382abaeb8390a, =6.1f7e698e326b239a91ea15844817551921209e826, 15d3a2a71c8bf7333d019d249ee33669e69e4275, 49193dac48d30eee2a21da88a7262d52a7feefae, 54a58d6656dd403b686b247f0bad8507cbfb45df, b1d7c69e6c7d3ec47513b911ce7529e56d183dad, e9f2160081a1e3ebb285bd71be3382abaeb8390a
linux-kernel: Kernel>=6.13.0 <6.18.51, >=6.19.0 <7.2.4, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114, >=6.1.0 <6.1.1916.18.51, 7.2.4, 6.6.160, 6.12.114, 6.1.191

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89757 severity on Zeptric[![CVE-2026-89757](https://zeptric.io/badge/cve/CVE-2026-89757.svg)](https://zeptric.io/cve/CVE-2026-89757)