{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89985 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89985 is a high-severity vulnerability in Linux, published on 16 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-89985 and fix it if it is affected.\n\nWhat it is: CVE-2026-89985 is a high-severity vulnerability in Linux, published on 16 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-89985 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-89985/ (Markdown: https://insights.sbomify.com/CVE-2026-89985/index.md)","id":"CVE-2026-89985","markdown":"https://insights.sbomify.com/CVE-2026-89985/index.md","name":"CVE-2026-89985","record":{"aliases":["DEBIAN-CVE-2026-89985","GHSA-5r45-xw38-xrg8","UBUNTU-CVE-2026-89985"],"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 reparenting can cause lock mismatches, potentially leading to system crashes or denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg: keep folio's objcg same as its node\n\nmemcg_reparent_objcgs() has an inherent assumption that a folio's objcg is\nthe objcg of the folio's node.  Folio migration across nodes breaks that\nassumption: the new folio simply inherits the old folio's objcg while\nliving on a different node.\n\nOnce the assumption is broken, the reparenting of the folio's objcg and\nthe reparenting of the folio's LRU list are no longer atomic. \nmemcg_reparent_objcgs() handles one node per iteration and drops all the\nlocks in between, so the objcg gets reparented in the iteration for the\nobjcg's node while the LRU list gets spliced in the iteration for the\nfolio's node.  Any LRU operation on that folio in between resolves its\nlruvec through the objcg, and thus takes the lru_lock of the wrong memcg,\nnot the lru_lock of the list the folio is actually on.\n\nFix this by selecting the objcg by folio_nid() at charge time, and by\nre-deriving it for the destination node in mem_cgroup_migrate() and\nmem_cgroup_replace_folio().","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":"memcg: keep folio's objcg same as its node","id":"CVE-2026-89985","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"mm/mempolicy: fix sleeping allocation in alloc_pages_bulk_weighted_interleave()","id":"CVE-2026-89986"},"packages":[],"prev":{"headline":"perf/x86/intel: Fix kernel address leakages in LBR stack","id":"CVE-2026-89984"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"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 reparenting can cause lock mismatches, potentially leading to system crashes or denial of service.","url":"https://insights.sbomify.com/CVE-2026-89985/"}