{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72180 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72180 is a 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-72180 and fix it if it is affected.\n\nWhat it is: CVE-2026-72180 is a 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-72180 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-72180/ (Markdown: https://insights.sbomify.com/CVE-2026-72180/index.md)","id":"CVE-2026-72180","markdown":"https://insights.sbomify.com/CVE-2026-72180/index.md","name":"CVE-2026-72180","record":{"aliases":["DEBIAN-CVE-2026-72180","GHSA-fr6m-54gx-w628","UBUNTU-CVE-2026-72180"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can bypass userfaultfd write protection on device-private huge pages by triggering a PMD downgrade, potentially evading memory monitoring.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"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: preserve pmd_swp_uffd_wp on device-private PMD downgrade\n\nchange_non_present_huge_pmd() rewrites a writable device-private PMD swap\nentry into a readable one without carrying pmd_swp_uffd_wp() across.  The\nPTE-level change_softleaf_pte() does this correctly; mirror that here,\nmatching what copy_huge_pmd() does for the fork path.  Without the carry,\na plain mprotect() over a UFFD_WP-marked device-private THP strips the bit\nand the trap is bypassed on swap-in.","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: preserve pmd_swp_uffd_wp on device-private PMD downgrade","id":"CVE-2026-72180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"mips: sched: Fix CPUMASK_OFFSTACK memory corruption","id":"CVE-2026-72181"},"packages":[],"prev":{"headline":"riscv: cacheinfo: Fix node reference leak in populate_cache_leaves","id":"CVE-2026-72179"},"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 local attacker can bypass userfaultfd write protection on device-private huge pages by triggering a PMD downgrade, potentially evading memory monitoring.","url":"https://insights.sbomify.com/CVE-2026-72180/"}