Answer in brief
CVE-2026-64286 records a Unknown severity vulnerability in KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU. 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 | >=be66e67f175096f283c9d5614c4991fc9e7ed975 <477145860dba4c30f0b4e36f02f4c5291c1c888b || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <dfaef40d8a1533940fc1af788d70fce07362b4ce || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <d4f4d61715d1061ba83b88196a3605662be30750 || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <e8042f6e1d7befb2fb6b10a75918642bcd0acf9a | 477145860dba4c30f0b4e36f02f4c5291c1c888b, dfaef40d8a1533940fc1af788d70fce07362b4ce, 6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa, d4f4d61715d1061ba83b88196a3605662be30750, e8042f6e1d7befb2fb6b10a75918642bcd0acf9a |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vCPU context into the hyp's private vCPU on every run. ctxt_to_vcpu() expects a guest context to have a NULL __hyp_running_vcpu, which is only ever set on the host context, so that it resolves the vCPU via container_of(). While this is generally the case, flush_hyp_vcpu() copies the context verbatim and does not enforce this, so a value provided by the host is dereferenced at EL2 (host -> EL2). Fix by clearing __hyp_running_vcpu after the copy.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64286 records a Unknown severity vulnerability in KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU. 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 | >=be66e67f175096f283c9d5614c4991fc9e7ed975 <477145860dba4c30f0b4e36f02f4c5291c1c888b || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <dfaef40d8a1533940fc1af788d70fce07362b4ce || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <d4f4d61715d1061ba83b88196a3605662be30750 || >=be66e67f175096f283c9d5614c4991fc9e7ed975 <e8042f6e1d7befb2fb6b10a75918642bcd0acf9a | 477145860dba4c30f0b4e36f02f4c5291c1c888b, dfaef40d8a1533940fc1af788d70fce07362b4ce, 6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa, d4f4d61715d1061ba83b88196a3605662be30750, e8042f6e1d7befb2fb6b10a75918642bcd0acf9a |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vCPU context into the hyp's private vCPU on every run. ctxt_to_vcpu() expects a guest context to have a NULL __hyp_running_vcpu, which is only ever set on the host context, so that it resolves the vCPU via container_of(). While this is generally the case, flush_hyp_vcpu() copies the context verbatim and does not enforce this, so a value provided by the host is dereferenced at EL2 (host -> EL2). Fix by clearing __hyp_running_vcpu after the copy.
Quoted source text, attributed separately from HOL analysis.