Linux
KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2a359e072596fcb2e9e85017a865e3618a2fe5b5, < 5c50db5bcbb9073cb2fd97be51b962de92f429e9
- >= 2a359e072596fcb2e9e85017a865e3618a2fe5b5, < d35defbdfcb15296ebe28968ad7452c1a8c11cea
- >= 2a359e072596fcb2e9e85017a865e3618a2fe5b5, < 2684e02bac41c5220f6c1ab2bdcc957b71812977
Fixed in 5c50db5bcbb9073cb2fd97be51b962de92f429e9, d35defbdfcb15296ebe28968ad7452c1a8c11cea, 2684e02bac41c5220f6c1ab2bdcc957b71812977
- 6.16
Fixed in 0, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to 5c50db5bcbb9073cb2fd97be51b962de92f429e9 or d35defbdfcb15296ebe28968ad7452c1a8c11cea or 2684e02bac41c5220f6c1ab2bdcc957b71812977 or later.
Upgrade Linux to 0 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.