Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 4 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU

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.

Affected products

Linux
  • <d4f4d61715d1061ba83b88196a3605662be30750
  • <e8042f6e1d7befb2fb6b10a75918642bcd0acf9a
  • ==6.2
  • =<6.18.*
  • <477145860dba4c30f0b4e36f02f4c5291c1c888b
  • =<6.12.*
  • =<7.1.*
  • =<*
  • =<6.6.*
  • <6.2
  • <dfaef40d8a1533940fc1af788d70fce07362b4ce
  • <6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa