KVM: s390: Fix memory corruption by not reinjecting CK machine checks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.114, 6.18.51, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4d62fcc0b692e3b4058d7d138114c27cd8b011f7 · fixed in 5c63e2ed840c85e27172ab78e7db3ac77fba281b; From 4d62fcc0b692e3b4058d7d138114c27cd8b011f7 · fixed in b7631982fb65dd355acd18e62b384bc8125e9c44; From 4d62fcc0b692e3b4058d7d138114c27cd8b011f7 · fixed in 6ee52d3af2a1bf70349cf3f860933c8d221e229a; From 4d62fcc0b692e3b4058d7d138114c27cd8b011f7 · fixed in 7077ec953996acc04b49d1dfc43df1c1a2a74395; From 4d62fcc0b692e3b4058d7d138114c27cd8b011f7 · fixed in 546dde823a36d7283dcf46127c2f3d093443860f
- Linux Linux
4.13
- KernelLinux
From 4.13.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5