https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 04:04:27 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64286 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU</p> <p>flush_hyp_vcpu() copies the host vCPU context into the hyp&#39;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 -&gt; EL2).</p> <p>Fix by clearing __hyp_running_vcpu after the copy.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU</p> <p>flush_hyp_vcpu() copies the host vCPU context into the hyp&#39;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 -&gt; EL2).</p> <p>Fix by clearing __hyp_running_vcpu after the copy.</p> https://vulnerability.circl.lu/vuln/cve-2026-64286