CVE-2022-26354: Low severity Qemu Qemu vulnerability
A flaw was found in the vhost-vsock device of QEMU. In case of error, an invalid element was not detached from the virtqueue before freeing its memory, leading to memory leakage and other unexpected results. Affected QEMU versions <= 6.2.0.
Other sources
A flaw was found in the vhost-vsock device of QEMU. In case of error, vhostvsockcommonsendtransportreset() did not detach the invalid element from the virtqueue before freeing its memory, leading to memory leakage or other unexpected results.
Upstream commit: https://gitlab.com/qemu-project/qemu/-/commit/8d1b247f3748ac4078524130c6d7ae42b6140aaf
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/qemuto a version that resolves this vulnerability.Fixed in 1:5.2+dfsg-11+deb11u3Fixed in 1:5.2+dfsg-11+deb11u2Fixed in 1:7.2+dfsg-7+deb12u12Fixed in 1:10.0.0~rc2+ds-2Fixed in 1:10.0.0~rc3+ds-2 - Upgrade
Upgrade
QEMUto a version that resolves this vulnerability.Patch 8d1b247f3748ac4078524130c6d7ae42b6140aaf
Event History
Frequently Asked Questions
What is the vulnerability ID of this flaw?
The vulnerability ID of this flaw is CVE-2022-26354.
What is the affected software?
The affected software includes QEMU versions <= 6.2.0, Debian Linux 9.0, Debian Linux 10.0, and certain versions of the QEMU package on Ubuntu and Debian.
What is the severity of CVE-2022-26354?
The severity of CVE-2022-26354 is low, with a severity value of 3.2.
What are the potential consequences of this vulnerability?
The potential consequences of this vulnerability include memory leakage and other unexpected results.
How can I fix CVE-2022-26354?
To fix CVE-2022-26354, you should update to a version of QEMU that is greater than 6.2.0, or apply the appropriate security patches for your operating system.