diff options
| author | Sean Christopherson <seanjc@google.com> | 2025-12-30 13:13:43 -0800 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-01-13 17:37:03 -0800 |
| commit | 405fce694bd1589082a7ffd500b5a4b841c22f0d (patch) | |
| tree | 419c6e768080e055ca831dd9cdd0b83e95ccaee2 /rust/alloc/collections/git@git.tavy.me:linux.git | |
| parent | 194c17bf5ebadd2fcf52ac641793e3d755a7af55 (diff) | |
KVM: SVM: Filter out 64-bit exit codes when invoking exit handlers on bare metal
Explicitly filter out 64-bit exit codes when invoking exit handlers, as
svm_exit_handlers[] will never be sized with entries that use bits 63:32.
Processing the non-failing exit code as a 32-bit value will allow tracking
exit_code as a single 64-bit value (which it is, architecturally). This
will also allow hardening KVM against Spectre-like attacks without needing
to do silly things to avoid build failures on 32-bit kernels
(array_index_nospec() rightly asserts that the index fits in an "unsigned
long").
Omit the check when running as a VM, as KVM has historically failed to set
bits 63:32 appropriately when synthesizing VM-Exits, i.e. KVM could get
false positives when running as a VM on an older, broken KVM/kernel. From
a functional perspective, omitting the check is "fine", as any unwanted
collision between e.g. VMEXIT_INVALID and a 32-bit exit code will be
fatal to KVM-on-KVM regardless of what KVM-as-L1 does.
Reviewed-by: Yosry Ahmed <yosry.ahmed@linux.dev>
Link: https://patch.msgid.link/20251230211347.4099600-5-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'rust/alloc/collections/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
