{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89752 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89752 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89752 and fix it if it is affected.\n\nWhat it is: CVE-2026-89752 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89752 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89752/ (Markdown: https://insights.sbomify.com/CVE-2026-89752/index.md)","id":"CVE-2026-89752","markdown":"https://insights.sbomify.com/CVE-2026-89752/index.md","name":"CVE-2026-89752","record":{"aliases":["AZL-100536","BELL-CVE-2026-89752","DEBIAN-CVE-2026-89752","GHSA-8w7m-rmxj-xxh8","UBUNTU-CVE-2026-89752"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in Linux kernel memory cgroup reclaim allows local attackers to cause indefinite loops and denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mm: memcg: stop reclaim when a limit update is superseded","id":"CVE-2026-89752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"mm/vmscan: report RCU-tasks quiescent states in shrink_lruvec()","id":"CVE-2026-89753"},"packages":[],"prev":{"headline":"x86/tdx: Fix off-by-one in port I/O handling","id":"CVE-2026-89751"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in Linux kernel memory cgroup reclaim allows local attackers to cause indefinite loops and denial of service.","url":"https://insights.sbomify.com/CVE-2026-89752/"}