{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72212 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72212 is a memory corruption vulnerability in Linux, published on 15 Aug 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-72212 and fix it if it is affected.\n\nWhat it is: CVE-2026-72212 is a memory corruption vulnerability in Linux, published on 15 Aug 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-72212 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-72212/ (Markdown: https://insights.sbomify.com/CVE-2026-72212/index.md)","id":"CVE-2026-72212","markdown":"https://insights.sbomify.com/CVE-2026-72212/index.md","name":"CVE-2026-72212","record":{"aliases":["BELL-CVE-2026-72212","DEBIAN-CVE-2026-72212","GHSA-w9xv-r954-cxrq","UBUNTU-CVE-2026-72212"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A bug in the Linux kernel memory hotplug error path causes memory corruption and potential code execution when memmap_on_memory is enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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/memory_hotplug: fix incorrect altmap passing in error path\n\nIn create_altmaps_and_memory_blocks(), when arch_add_memory() succeeds\nwith memmap_on_memory enabled, the vmemmap pages are allocated from\nparams.altmap.  If create_memory_block_devices() subsequently fails, the\nerror path calls arch_remove_memory() with a NULL altmap instead of\nparams.altmap.\n\nThis is a bug that could lead to memory corruption.  Since altmap is NULL,\nvmemmap_free() falls back to freeing the vmemmap pages into the system\nbuddy allocator via free_pages() instead of the altmap. \narch_remove_memory() then immediately destroys the physical linear mapping\nfor this memory.  This injects unowned pages into the buddy allocator,\ncausing machine checks or memory corruption if the system later attempts\nto allocate and use those freed pages.\n\nFix this by passing params.altmap to arch_remove_memory() in the error\npath.","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/memory_hotplug: fix incorrect altmap passing in error path","id":"CVE-2026-72212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch","id":"CVE-2026-72213"},"packages":[],"prev":{"headline":"ntfs: grow index root value before reparent header update","id":"CVE-2026-72211"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A bug in the Linux kernel memory hotplug error path causes memory corruption and potential code execution when memmap_on_memory is enabled.","url":"https://insights.sbomify.com/CVE-2026-72212/"}