CVE-2022-26353: Use After Free
A flaw was found in the virtio-net device of QEMU. This flaw was inadvertently introduced with the fix for CVE-2021-3748, which forgot to unmap the cached virtqueue elements on error, leading to memory leakage and other unexpected results. Affected QEMU version: 6.2.0.
Other sources
Commit bedd7e93d0196 ("virtio-net: fix use after unmap/free for sg") tries to fix the use after free of the sg by caching the virtqueue elements in an array and unmap them at once after receiving the packets, But it forgot to unmap the cached elements on error which will lead to leaking of mapping and other unexpected results.
Upstream patch: https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg02438.html
— 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 bedd7e93d0196
Event History
Frequently Asked Questions
What is the vulnerability ID for this flaw?
The vulnerability ID for this flaw is CVE-2022-26353.
What is the severity of CVE-2022-26353?
The severity of CVE-2022-26353 is high with a severity value of 7.5.
Which versions of QEMU are affected by CVE-2022-26353?
QEMU version 6.2.0 is affected by CVE-2022-26353.
How was CVE-2022-26353 introduced?
CVE-2022-26353 was inadvertently introduced with the fix for CVE-2021-3748.
Are there any known fixes for CVE-2022-26353?
Yes, there are known fixes available. Please refer to the provided references for more information.