{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72279 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72279 is a critical 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-72279 and fix it if it is affected.\n\nWhat it is: CVE-2026-72279 is a critical 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-72279 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-72279/ (Markdown: https://insights.sbomify.com/CVE-2026-72279/index.md)","id":"CVE-2026-72279","markdown":"https://insights.sbomify.com/CVE-2026-72279/index.md","name":"CVE-2026-72279","record":{"aliases":["BELL-CVE-2026-72279","DEBIAN-CVE-2026-72279","GHSA-3627-jjwg-8vfw","UBUNTU-CVE-2026-72279"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel KVM","requires_auth":"none","summary":"A flaw in Linux KVM arm64 nested virtualization allows guest writes to read-only memory, potentially enabling privilege escalation or data modification.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR\n\nKVM currently maps the L1 VNCR into the host stage-1 by relying entirely\non the permissions of the guest stage-1. At the same time, it is\nentirely possible that the backing PFN is read-only (e.g. RO memslot),\nmeaning that the L1 VNCR should use at most a read-only mapping.\n\nCache the writability of the PFN in the VNCR TLB and use it to constrain\nthe resulting fixmap permissions. Promote VNCR permission faults to an\nSEA in the case where the guest attempts to write to a read-only\nendpoint. Conveniently, this also plugs a page leak found by Sashiko [*]\nresulting from the early return for a read-only PFN.","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":"KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR","id":"CVE-2026-72279","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL2","id":"CVE-2026-72280"},"packages":[],"prev":{"headline":"KVM: arm64: nv: Re-translate VNCR before injecting abort","id":"CVE-2026-72278"},"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 Linux KVM arm64 nested virtualization allows guest writes to read-only memory, potentially enabling privilege escalation or data modification.","url":"https://insights.sbomify.com/CVE-2026-72279/"}