KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler
We do check for target CPU == -1, but this might change at the time we are going to use it. Hold the physical target CPU in a local variable to avoid out-of-bound accesses to the cpu arrays.
From the CVE record · Linux
The Linux kernel’s KVM s390 diag 9c handler can use a physical target CPU number after it changes, causing out-of-bounds access to CPU arrays. This can occur when the number changes between the check and its use. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the KVM s390 diag 9c handler should check their deployments; affected versions are not specified.