{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80729 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80729 is a vulnerability in Linux, published on 3 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-80729 and fix it if it is affected.\n\nWhat it is: CVE-2026-80729 is a vulnerability in Linux, published on 3 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-80729 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-80729/ (Markdown: https://insights.sbomify.com/CVE-2026-80729/index.md)","id":"CVE-2026-80729","markdown":"https://insights.sbomify.com/CVE-2026-80729/index.md","name":"CVE-2026-80729","record":{"aliases":["BELL-CVE-2026-80729","DEBIAN-CVE-2026-80729","GHSA-p2p8-6fmx-rfj9","UBUNTU-CVE-2026-80729"],"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":"none","summary":"A missing initialization in the Linux kernel memory management subsystem can cause a kernel warning and potential denial of service during memory reclaim.","user_interaction":"not_required","vuln_class":"null_dereference"},"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/huge_memory: initialise workingset state before folio split\n\nxas_try_split() adds __GFP_ACCOUNT for page-cache xa_nodes, but\n__folio_split() leaves the xa_state's xa_lru unset.  That lets a live,\nmemcg-charged xa_node exist without being linked into the mapping's\nshadow_nodes list_lru; when reclaim later walks the list_lru it trips\nVM_WARN_ON(!css_is_dying()).\n\nUse mapping_set_update() to install both the workingset update callback\nand the shadow_nodes list_lru on the xa_state.","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/huge_memory: initialise workingset state before folio split","id":"CVE-2026-80729","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ring-buffer: Fix crash passing ERR_PTR to kthread_stop()","id":"CVE-2026-80730"},"packages":[],"prev":{"headline":"Revert \"drm/amdgpu: fix aperture mapping leak\"","id":"CVE-2026-80728"},"products":["Linux"],"published":"2026-09-03","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-11","vendors":["Linux"]},"summary":"A missing initialization in the Linux kernel memory management subsystem can cause a kernel warning and potential denial of service during memory reclaim.","url":"https://insights.sbomify.com/CVE-2026-80729/"}