Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR KVM currently maps the L1 VNCR into the host stage-1 by relying entirely on the permissions of the guest stage-1. At the same time, it is entirely possible that the backing PFN is read-only (e.g. RO memslot), meaning that the L1 VNCR should use at most a read-only mapping. Cache the writability of the PFN in the VNCR TLB and use it to constrain the resulting fixmap permissions. Promote VNCR permission faults to an SEA in the case where the guest attempts to write to a read-only endpoint. Conveniently, this also plugs a page leak found by Sashiko [*] resulting from the early return for a read-only PFN.
CVSS Score
CRITICAL
References
- https://git.kernel.org/stable/c/2684e02bac41c5220f6c1ab2bdcc957b71812977
- https://git.kernel.org/stable/c/5c50db5bcbb9073cb2fd97be51b962de92f429e9
- https://git.kernel.org/stable/c/d35defbdfcb15296ebe28968ad7452c1a8c11cea
FAQ
What is CVE-2026-72279?
CVE-2026-72279 is a vulnerability with a CVSS score of 9.0 (CRITICAL). In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR KVM currently maps the L1 VNCR into the host stage-1 by relying entirel...
How severe is CVE-2026-72279?
CVE-2026-72279 has been rated CRITICAL with a CVSS base score of 9.0/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-72279?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.