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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
2a359e072596fcb2e9e85017a865e3618a2fe5b5 to < 5c50db5bcbb9073cb2fd97be51b962de92f429e9affected2a359e072596fcb2e9e85017a865e3618a2fe5b5 to < d35defbdfcb15296ebe28968ad7452c1a8c11ceaaffected2a359e072596fcb2e9e85017a865e3618a2fe5b5 to < 2684e02bac41c5220f6c1ab2bdcc957b71812977affected
Linux Linux
Default version status: affected
6.16affected0 to < 6.16unaffected6.18.40 to ≤ 6.18.*unaffected7.1.5 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected