KVM: s390: Fix memory corruption by not reinjecting CK machine checks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4d62fcc0b692e3b4058d7d138114c27cd8b011f7 · < 546dde823a36d7283dcf46127c2f3d093443860f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: Fix memory corruption by not reinjecting CK machine checks
Channel-subsystem damage machine checks are for the host channel subsystem. The guest channel subsystem is emulated in the userspace VMM. There is no point in forwarding such machine checks into the guest.
This also simplifies the machine check reinjection and avoids kfree of a stack variable as reported by sashiko. There might be still machine checks that have the ck bit set with another bit (like instruction damage), mask out the CK bit in s390_backup_mcck_info(), like the CP and ED bits already are.
From the CVE record · Linux
KVM on s390 can corrupt memory when reinjecting channel-subsystem damage machine checks into a guest. The report describes a possible free of a stack variable; it does not specify attacker access requirements or whether user interaction is needed.
Engineers running the Linux kernel with KVM on s390 should check their systems; affected versions are not specified.