KVM: s390: Zero initialize data structures for inject_pfault_token
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 383d0b050106abecb82f43101cac94fa423af5cd · < 9b046de62b8098af6e2ba820b125ec9dc5f162c8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: Zero initialize data structures for inject_pfault_token
__kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values.
Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data.
Fix by zero-initializing the irq struct. Do the same for the inti data structure.
From the CVE record · Linux
KVM s390 leaves stale stack values in an interrupt structure used for fault-token injection. A local host user can access those values through migration ioctls; interrupt delivery does not leak them to the guest.
Operators running Linux kernels with KVM s390 should check their systems; affected versions were not provided.