Answer in brief
CVE-2026-72277 records a Unknown severity vulnerability in KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory. 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 <d5436e18e4fc2886ac306304d884ea3b92e1edbf || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <bc00e0e376ee3572f5d26c174473abef1e35decc || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6 | d5436e18e4fc2886ac306304d884ea3b92e1edbf, bc00e0e376ee3572f5d26c174473abef1e35decc, 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6 |
| 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: Inject SEA if guest VNCR isn't normal memory When constructing an L1 VNCR mapping, KVM unconditionally uses cacheable memory attributes, even if the underlying PFN isn't memory. This gets particularly hairy if the endpoint doesn't support cacheable memory attributes, potentially throwing an SError on writeback... While KVM does permit cacheable memory attributes on certain PFNMAP VMAs, kvm_translate_vncr() isn't currently grabbing the VMA. So do the simpler thing for now and just reject everything that isn't memory.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72277 records a Unknown severity vulnerability in KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory. 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 <d5436e18e4fc2886ac306304d884ea3b92e1edbf || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <bc00e0e376ee3572f5d26c174473abef1e35decc || >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6 | d5436e18e4fc2886ac306304d884ea3b92e1edbf, bc00e0e376ee3572f5d26c174473abef1e35decc, 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6 |
| 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: Inject SEA if guest VNCR isn't normal memory When constructing an L1 VNCR mapping, KVM unconditionally uses cacheable memory attributes, even if the underlying PFN isn't memory. This gets particularly hairy if the endpoint doesn't support cacheable memory attributes, potentially throwing an SError on writeback... While KVM does permit cacheable memory attributes on certain PFNMAP VMAs, kvm_translate_vncr() isn't currently grabbing the VMA. So do the simpler thing for now and just reject everything that isn't memory.
Quoted source text, attributed separately from HOL analysis.