{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72412 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72412 is a critical 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-72412 and fix it if it is affected.\n\nWhat it is: CVE-2026-72412 is a critical 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-72412 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-72412/ (Markdown: https://insights.sbomify.com/CVE-2026-72412/index.md)","id":"CVE-2026-72412","markdown":"https://insights.sbomify.com/CVE-2026-72412/index.md","name":"CVE-2026-72412","record":{"aliases":["DEBIAN-CVE-2026-72412","GHSA-94jh-p9fj-qxf8","UBUNTU-CVE-2026-72412"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel s390","requires_auth":"none","summary":"A flaw in the Linux kernel s390 memory management allows guest memory corruption and potential denial of service due to improper handling of the _PAGE_UNUSED bit.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/mm: Fix handling of _PAGE_UNUSED pte bit\n\nThe _PAGE_UNUSED softbit should not really be lying around. Its sole\npurpose is to signal to try_to_unmap_one() and try_to_migrate_one()\nthat the page can be discarded instead of being moved / swapped.\n\nKVM has no way to know why a page is being unmapped, so it sets the bit\non userspace ptes corresponding to unused guest pages every time they\nget unmapped. KVM has no reasonable way to clear the bit once the page\nis in use again.\n\nWhile set_ptes() checks and clears the bit, other paths that set new\nptes did not. This led to used pages being thrown out as if they were\nunused, causing guest corruption.\n\nFix the issue by clearing the _PAGE_UNUSED bit for present ptes in\nset_pte(), i.e. whenever a present pte is getting set. The check in\nset_ptes() is then redundant and can be removed.\n\nAlso fix gmap_helper_try_set_pte_unused() to only set the bit if the\npte is present; the _PAGE_UNUSED bit is only defined for present ptes\nand thus should not be set for non-present ptes.","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":"s390/mm: Fix handling of _PAGE_UNUSED pte bit","id":"CVE-2026-72412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"sctp: fix err_chunk memory leaks in INIT handling","id":"CVE-2026-72413"},"packages":[],"prev":{"headline":"net: dsa: mxl862xx: fix use-after-free of DSA ports in crc_err_work","id":"CVE-2026-72411"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A flaw in the Linux kernel s390 memory management allows guest memory corruption and potential denial of service due to improper handling of the _PAGE_UNUSED bit.","url":"https://insights.sbomify.com/CVE-2026-72412/"}