Answer in brief
CVE-2026-64288 records a Medium severity (CVSS 5.5) vulnerability in KVM: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB. 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.
CVSS is 5.5. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <7c73a269a880b1399baacfb9d521415e6ef7ecc2 || >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <5fd30133af864a1de0a0bd87d3fe3cf23205fbc7 || >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <4be6cbeb93d26994bd1827ddbce391e3c4395c8f | 7c73a269a880b1399baacfb9d521415e6ef7ecc2, 5fd30133af864a1de0a0bd87d3fe3cf23205fbc7, 4be6cbeb93d26994bd1827ddbce391e3c4395c8f |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB VNCR TLB invalidation occurs from MMU notifiers or TLBI instructions, and either can race against a vcpu not being onlined yet (no pseudo-TLB allocated). Similarly, the TLB might be invalid, and the invalidation should be skipped in this case. Both kvm_invalidate_vncr_ipa() and kvm_invalidate_vncr_va() are expected to perform the same checks, except that the latter doesn't check for the allocation and blindly dereferences the pointer. Solve this by introducing a new iterator built on top of the usual kvm_for_each_vcpu() that checks for both of the above conditions, and convert the two users to it.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64288 records a Medium severity (CVSS 5.5) vulnerability in KVM: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB. 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.
CVSS is 5.5. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <7c73a269a880b1399baacfb9d521415e6ef7ecc2 || >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <5fd30133af864a1de0a0bd87d3fe3cf23205fbc7 || >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <4be6cbeb93d26994bd1827ddbce391e3c4395c8f | 7c73a269a880b1399baacfb9d521415e6ef7ecc2, 5fd30133af864a1de0a0bd87d3fe3cf23205fbc7, 4be6cbeb93d26994bd1827ddbce391e3c4395c8f |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB VNCR TLB invalidation occurs from MMU notifiers or TLBI instructions, and either can race against a vcpu not being onlined yet (no pseudo-TLB allocated). Similarly, the TLB might be invalid, and the invalidation should be skipped in this case. Both kvm_invalidate_vncr_ipa() and kvm_invalidate_vncr_va() are expected to perform the same checks, except that the latter doesn't check for the allocation and blindly dereferences the pointer. Solve this by introducing a new iterator built on top of the usual kvm_for_each_vcpu() that checks for both of the above conditions, and convert the two users to it.
Quoted source text, attributed separately from HOL analysis.