mm: memcg: stop reclaim when a limit update is superseded
In the Linux kernel, the following vulnerability has been resolved: mm: memcg: stop reclaim when a limit update is superseded kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target. For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event. Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target. Reproducer: Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible. Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally. This was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
- Published
- Sep 11, 2026
- Updated
- Sep 14, 2026
- EPSS
- 0.2% · 7th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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
- 0ccab5b139971a2a3f48df24d1ee8be2dbf84042, 97729c37439040ec07807f0dbb71ea60ccbafd27, 4.6affected
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before ebf762a393630d1582645be3f0fc22a674eb9122affected · git
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before 4ea0617b9e46d26c0a3e5af00308ea1931cc545daffected · git
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before 5c6f87d33733d96fba66ea4e78cd8b24b4d60a49affected · git
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before 8bf21ad3657305e28deafd9ef16a121407496bc3affected · git
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before 39ec1e4183a718f448b2e9de681dcbdda18fce42affected · git
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before 95d87030cae7764805aa7c621c52871139297cb0affected · git
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before aab391074de96ed601eeca32daef9a8507d436d9affected · git
- b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f and later · before 9477820c63cbf4d97114238f3d1ff10dfd6bee3faffected · git
- 4.4.7 and later · before 4.5affected · 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 | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| 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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 39ec1e4183a718f448b2e9de681dcbdda18fce42 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4.6 | Vendor (CNA) |
| Linux Linux | 4ea0617b9e46d26c0a3e5af00308ea1931cc545d | Vendor (CNA) |
| Linux Linux | 5c6f87d33733d96fba66ea4e78cd8b24b4d60a49 | Vendor (CNA) |
| Linux Linux | 8bf21ad3657305e28deafd9ef16a121407496bc3 | Vendor (CNA) |
| Linux Linux | 9477820c63cbf4d97114238f3d1ff10dfd6bee3f | Vendor (CNA) |
| Linux Linux | 95d87030cae7764805aa7c621c52871139297cb0 | Vendor (CNA) |
| Linux Linux | aab391074de96ed601eeca32daef9a8507d436d9 | Vendor (CNA) |
| Linux Linux | ebf762a393630d1582645be3f0fc22a674eb9122 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~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).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/39ec1e4183a718f448b2e9de681dcbdda18fce42
- git.kernel.org/stable/c/4ea0617b9e46d26c0a3e5af00308ea1931cc545d
- git.kernel.org/stable/c/5c6f87d33733d96fba66ea4e78cd8b24b4d60a49
- git.kernel.org/stable/c/8bf21ad3657305e28deafd9ef16a121407496bc3
- git.kernel.org/stable/c/9477820c63cbf4d97114238f3d1ff10dfd6bee3f
- git.kernel.org/stable/c/95d87030cae7764805aa7c621c52871139297cb0
- git.kernel.org/stable/c/aab391074de96ed601eeca32daef9a8507d436d9
- git.kernel.org/stable/c/ebf762a393630d1582645be3f0fc22a674eb9122
Vendor advisories and official records. Exploit/PoC links are deliberately left out.