KVM: s390: pci: Validate AIBV and AISB before pinning guest pages
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc · < 868d32ac72cba21c5c6d8a66a814b7c25a3a5c01| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: pci: Validate AIBV and AISB before pinning guest pages
The AIBV holds one bit per MSI-X vector for a given function. The size of the bit vector is derived from the NOI and the AIBVO. If the size of the AIBV exceeds a single page boundary, then reject the request as we cannot safely pin the guest AIBV.
Similarly reject the request if the AISB address is not 8-byte aligned as the architecture requires doubleword alignment for the summary bit address. Since the AISBO can address up to 64 bits, the size of the AISB can only be 8 bytes for the function. This also ensures the AISB doesn't exceed a single page boundary.
From the CVE record · Linux
KVM on s390 did not validate the AIBV size and AISB alignment before pinning guest pages. A guest request with an AIBV spanning a page boundary could lead to unsafe pinning; an AISB address that is not 8-byte aligned also violates the architecture's requirements. The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with KVM on s390 and PCI support should check their versions against the vendor advisory; affected versions are not specified.