Answer in brief
CVE-2026-72279 records a Unknown severity vulnerability in KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <5c50db5bcbb9073cb2fd97be51b962de92f429e9 || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <d35defbdfcb15296ebe28968ad7452c1a8c11cea || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <2684e02bac41c5220f6c1ab2bdcc957b71812977 | 5c50db5bcbb9073cb2fd97be51b962de92f429e9, d35defbdfcb15296ebe28968ad7452c1a8c11cea, 2684e02bac41c5220f6c1ab2bdcc957b71812977 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72279 records a Unknown severity vulnerability in KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <5c50db5bcbb9073cb2fd97be51b962de92f429e9 || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <d35defbdfcb15296ebe28968ad7452c1a8c11cea || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <2684e02bac41c5220f6c1ab2bdcc957b71812977 | 5c50db5bcbb9073cb2fd97be51b962de92f429e9, d35defbdfcb15296ebe28968ad7452c1a8c11cea, 2684e02bac41c5220f6c1ab2bdcc957b71812977 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.