CVE-2026-89757: mm/mglru: fix and remove redundant unevictable folio handling
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 15d3a2a71c8bf7333d019d249ee33669e69e4275, 49193dac48d30eee2a21da88a7262d52a7feefae, 54a58d6656dd403b686b247f0bad8507cbfb45df; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 15d3a2a71c8bf7333d019d249ee33669e69e4275, 49193dac48d30eee2a21da88a7262d52a7feefae, 54a58d6656dd403b686b247f0bad8507cbfb45df; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.1affected
- ac35a490237446b71e3b4b782b1596967edd0aa8 and later · before e9f2160081a1e3ebb285bd71be3382abaeb8390aaffected · git
- ac35a490237446b71e3b4b782b1596967edd0aa8 and later · before b1d7c69e6c7d3ec47513b911ce7529e56d183dadaffected · git
- ac35a490237446b71e3b4b782b1596967edd0aa8 and later · before 49193dac48d30eee2a21da88a7262d52a7feefaeaffected · git
- ac35a490237446b71e3b4b782b1596967edd0aa8 and later · before 54a58d6656dd403b686b247f0bad8507cbfb45dfaffected · git
- ac35a490237446b71e3b4b782b1596967edd0aa8 and later · before 15d3a2a71c8bf7333d019d249ee33669e69e4275affected · git
- ac35a490237446b71e3b4b782b1596967edd0aa8 and later · before f7e698e326b239a91ea15844817551921209e826affected · git
- before 6.1not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:12 | linux-6.12 | before 6.12.115-2~deb12u1 | 6.12.115-2~deb12u1 |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89755Sep 11, 2026 · mm/migrate_device: clear stale mapping after freeing swapcache31Monitor
- ← EarlierCVE-2026-89756Sep 11, 2026 · mm/migrate: report RCU-tasks quiescent states in migrate_pages_batch()0Monitor
- Later →CVE-2026-89758Sep 11, 2026 · mm/mempolicy: skip non-present PMDs when queueing folios31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 15d3a2a71c8bf7333d019d249ee33669e69e4275 | Vendor (CNA) |
| Linux Linux | 49193dac48d30eee2a21da88a7262d52a7feefae | Vendor (CNA) |
| Linux Linux | 54a58d6656dd403b686b247f0bad8507cbfb45df | Vendor (CNA) |
| Linux Linux | b1d7c69e6c7d3ec47513b911ce7529e56d183dad | Vendor (CNA) |
| Linux Linux | e9f2160081a1e3ebb285bd71be3382abaeb8390a | Vendor (CNA) |
| Linux Linux | f7e698e326b239a91ea15844817551921209e826 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | 0:6.18.57-1.1.azl4 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.115-2~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/49193dac48d30eee2a21da88a7262d52a7feefae
- git.kernel.org/stable/c/54a58d6656dd403b686b247f0bad8507cbfb45df
- git.kernel.org/stable/c/b1d7c69e6c7d3ec47513b911ce7529e56d183dad
- git.kernel.org/stable/c/e9f2160081a1e3ebb285bd71be3382abaeb8390a
- git.kernel.org/stable/c/f7e698e326b239a91ea15844817551921209e826
Vendor advisories and official records. Exploit/PoC links are deliberately left out.