{"api_version":"1","generated_at":"2026-09-11T21:38:11+00:00","cve":"CVE-2026-89752","urls":{"html":"https://cve.report/CVE-2026-89752","api":"https://cve.report/api/cve/CVE-2026-89752.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89752","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89752"},"summary":{"title":"mm: memcg: stop reclaim when a limit update is superseded","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm: memcg: stop reclaim when a limit update is superseded\n\nkernfs serializes file operations only per open file, so separate open\nfiles can update the same memory.high or memory.max file concurrently. \nBoth handlers store the new limit before synchronous reclaim, but continue\nto use the writer's local target in the reclaim loop.  If another writer\nraises or removes the limit, the first writer can continue reclaiming\ntoward a stale target.\n\nFor memory.max, this can leave the writer looping indefinitely once\nreclaim retries are exhausted.  The OOM path sees sufficient margin under\nthe current limit and returns true without killing, while the writer still\ncompares usage against its stale target and records another OOM event.\n\nCheck the current limit at the start of each reclaim iteration and stop if\nit no longer matches the writer's target.\n\nReproducer:\n\nPopulate a cgroup with anonymous memory and disable swapping.  Lower\nmemory.max from one open file, then restore it to \"max\" through another\nopen file after the new limit becomes visible.\n\nWithout the patch, the first writer remains blocked and repeatedly\nincrements the OOM event counter.  With the patch, it returns normally.\n\nThis was not motivated by a reported production workload.  We found it\nthrough automated randomized testing for our cgroup observability work\nand reduced it to the reproducer above.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:20:06","updated_at":"2026-09-11 20:20:06"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/9477820c63cbf4d97114238f3d1ff10dfd6bee3f","name":"https://git.kernel.org/stable/c/9477820c63cbf4d97114238f3d1ff10dfd6bee3f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/aab391074de96ed601eeca32daef9a8507d436d9","name":"https://git.kernel.org/stable/c/aab391074de96ed601eeca32daef9a8507d436d9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/39ec1e4183a718f448b2e9de681dcbdda18fce42","name":"https://git.kernel.org/stable/c/39ec1e4183a718f448b2e9de681dcbdda18fce42","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/95d87030cae7764805aa7c621c52871139297cb0","name":"https://git.kernel.org/stable/c/95d87030cae7764805aa7c621c52871139297cb0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89752","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89752","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f 39ec1e4183a718f448b2e9de681dcbdda18fce42 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f 95d87030cae7764805aa7c621c52871139297cb0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f aab391074de96ed601eeca32daef9a8507d436d9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f 9477820c63cbf4d97114238f3d1ff10dfd6bee3f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0ccab5b139971a2a3f48df24d1ee8be2dbf84042 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 97729c37439040ec07807f0dbb71ea60ccbafd27 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.4.7 4.5 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.5.1 4.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.109 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/memcontrol.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"39ec1e4183a718f448b2e9de681dcbdda18fce42","status":"affected","version":"b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f","versionType":"git"},{"lessThan":"95d87030cae7764805aa7c621c52871139297cb0","status":"affected","version":"b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f","versionType":"git"},{"lessThan":"aab391074de96ed601eeca32daef9a8507d436d9","status":"affected","version":"b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f","versionType":"git"},{"lessThan":"9477820c63cbf4d97114238f3d1ff10dfd6bee3f","status":"affected","version":"b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f","versionType":"git"},{"status":"affected","version":"0ccab5b139971a2a3f48df24d1ee8be2dbf84042","versionType":"git"},{"status":"affected","version":"97729c37439040ec07807f0dbb71ea60ccbafd27","versionType":"git"},{"lessThan":"4.5","status":"affected","version":"4.4.7","versionType":"semver"},{"lessThan":"4.6","status":"affected","version":"4.5.1","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/memcontrol.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.6"},{"lessThan":"4.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.109","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.109","versionStartIncluding":"4.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"4.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"4.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"4.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.4.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.5.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm: memcg: stop reclaim when a limit update is superseded\n\nkernfs serializes file operations only per open file, so separate open\nfiles can update the same memory.high or memory.max file concurrently. \nBoth handlers store the new limit before synchronous reclaim, but continue\nto use the writer's local target in the reclaim loop.  If another writer\nraises or removes the limit, the first writer can continue reclaiming\ntoward a stale target.\n\nFor memory.max, this can leave the writer looping indefinitely once\nreclaim retries are exhausted.  The OOM path sees sufficient margin under\nthe current limit and returns true without killing, while the writer still\ncompares usage against its stale target and records another OOM event.\n\nCheck the current limit at the start of each reclaim iteration and stop if\nit no longer matches the writer's target.\n\nReproducer:\n\nPopulate a cgroup with anonymous memory and disable swapping.  Lower\nmemory.max from one open file, then restore it to \"max\" through another\nopen file after the new limit becomes visible.\n\nWithout the patch, the first writer remains blocked and repeatedly\nincrements the OOM event counter.  With the patch, it returns normally.\n\nThis was not motivated by a reported production workload.  We found it\nthrough automated randomized testing for our cgroup observability work\nand reduced it to the reproducer above."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:46:56.059Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/39ec1e4183a718f448b2e9de681dcbdda18fce42"},{"url":"https://git.kernel.org/stable/c/95d87030cae7764805aa7c621c52871139297cb0"},{"url":"https://git.kernel.org/stable/c/aab391074de96ed601eeca32daef9a8507d436d9"},{"url":"https://git.kernel.org/stable/c/9477820c63cbf4d97114238f3d1ff10dfd6bee3f"}],"title":"mm: memcg: stop reclaim when a limit update is superseded","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89752","datePublished":"2026-09-11T19:46:56.059Z","dateReserved":"2026-09-11T19:38:34.763Z","dateUpdated":"2026-09-11T19:46:56.059Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:20:06","lastModifiedDate":"2026-09-11 20:20:06","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89752","Ordinal":"1","Title":"mm: memcg: stop reclaim when a limit update is superseded","CVE":"CVE-2026-89752","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89752","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm: memcg: stop reclaim when a limit update is superseded\n\nkernfs serializes file operations only per open file, so separate open\nfiles can update the same memory.high or memory.max file concurrently. \nBoth handlers store the new limit before synchronous reclaim, but continue\nto use the writer's local target in the reclaim loop.  If another writer\nraises or removes the limit, the first writer can continue reclaiming\ntoward a stale target.\n\nFor memory.max, this can leave the writer looping indefinitely once\nreclaim retries are exhausted.  The OOM path sees sufficient margin under\nthe current limit and returns true without killing, while the writer still\ncompares usage against its stale target and records another OOM event.\n\nCheck the current limit at the start of each reclaim iteration and stop if\nit no longer matches the writer's target.\n\nReproducer:\n\nPopulate a cgroup with anonymous memory and disable swapping.  Lower\nmemory.max from one open file, then restore it to \"max\" through another\nopen file after the new limit becomes visible.\n\nWithout the patch, the first writer remains blocked and repeatedly\nincrements the OOM event counter.  With the patch, it returns normally.\n\nThis was not motivated by a reported production workload.  We found it\nthrough automated randomized testing for our cgroup observability work\nand reduced it to the reproducer above.","Type":"Description","Title":"mm: memcg: stop reclaim when a limit update is superseded"}]}}}