KVM: s390: vsie: zero stale crypto bits
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6b79de4b056e5a2febc0c61233d8f0ad7868e49c · < 935eeba276012916c76243e5cbb843efd8fdb75d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: vsie: zero stale crypto bits
When shadowing crypto access bits from a format0 apcb (crycb 0 or 1), the bits 64..255 are unchanged from whatever is in the vsie page in the crycb and thus in the apcb. This gives a nested guest potential access to a device no longer available. Zero out the remaining bits.
From the CVE record · Linux
The Linux kernel’s KVM s390 vsie code can leave stale crypto access bits when shadowing a format0 crypto control block. A nested guest may gain access to a device that is no longer available to it. The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with KVM s390 nested guests should check their systems; affected versions are not specified.