CVE-2022-48727
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2022-48727
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48727.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2022-48727
- Related
- Published
- 2024-06-20T12:15:11Z
- Modified
- 2024-09-18T01:00:21Z
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Avoid consuming a stale esr value when SError occur
When any exception other than an IRQ occurs, the CPU updates the ESREL2 register with the exception syndrome. An SError may also become pending, and will be synchronised by KVM. KVM notes the exception type, and whether an SError was synchronised in exitcode.
When an exception other than an IRQ occurs, fixupguestexit() updates vcpu->arch.fault.esrel2 from the hardware register. When an SError was synchronised, the vcpu esr value is used to determine if the exception was due to an HVC. If so, ELREL2 is moved back one instruction. This is so that KVM can process the SError first, and re-execute the HVC if the guest survives the SError.
But if an IRQ synchronises an SError, the vcpu's esr value is stale. If the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2, causing an unrelated guest instruction to be executed twice.
Check ARMEXCEPTIONCODE() before messing with ELR_EL2, IRQs don't update this register so don't need to check.
- References
Affected packages
Debian:12 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source