CVE-2022-26353: Use After Free
First published: Fri Mar 11 2022(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| QEMU qemu | =6.2.0 | |
| Debian Debian Linux | =11.0 | |
| ubuntu/qemu | <1:2.11+dfsg-1ubuntu7.40 | 1:2.11+dfsg-1ubuntu7.40 |
| ubuntu/qemu | <1:4.2-3ubuntu6.23 | 1:4.2-3ubuntu6.23 |
| ubuntu/qemu | <1:6.2+dfsg-2ubuntu8 | 1:6.2+dfsg-2ubuntu8 |
| ubuntu/qemu | <1:6.0+dfsg-2 | 1:6.0+dfsg-2 |
| ubuntu/qemu | <1:6.2+dfsg-2ubuntu6.2 | 1:6.2+dfsg-2ubuntu6.2 |
| ubuntu/qemu | <1:6.2+dfsg-2ubuntu8 | 1:6.2+dfsg-2ubuntu8 |
| ubuntu/qemu | <1:6.2+dfsg-2ubuntu8 | 1:6.2+dfsg-2ubuntu8 |
| debian/qemu | 1:3.1+dfsg-8+deb10u8 1:3.1+dfsg-8+deb10u11 1:5.2+dfsg-11+deb11u3 1:5.2+dfsg-11+deb11u2 1:7.2+dfsg-7+deb12u3 1:8.2.1+ds-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg02438.html
- https://gitlab.com/qemu-project/qemu/-/commit/abe300d9d894f7138e1af7c8e9c88c04bfe98b37
- https://www.debian.org/security/2022/dsa-5133
- https://security.gentoo.org/glsa/202208-27
- https://security.netapp.com/advisory/ntap-20220425-0003/
- https://launchpad.net/bugs/cve/CVE-2022-26353
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2063199
- https://access.redhat.com/solutions/408653
- https://access.redhat.com/errata/RHSA-2022:5002
- https://access.redhat.com/errata/RHSA-2022:5263
- https://access.redhat.com/errata/RHSA-2022:5821
- https://access.redhat.com/security/cve/cve-2022-26353
- https://bugzilla.redhat.com/show_bug.cgi?id=2063197
- https://gitlab.com/qemu-project/qemu/-/commit/bedd7e93d01961fcb16a97ae45d93acf357e11f6
- https://security-tracker.debian.org/tracker/CVE-2022-26353
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26353
- https://ubuntu.com/security/notices/USN-5489-1
- https://nvd.nist.gov/vuln/detail/CVE-2022-26353
- https://git.qemu.org/?p=qemu.git;a=commit;h=abe300d9d894f7138e1af7c8e9c88c04bfe98b37
- https://ubuntu.com/security/CVE-2022-26353
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.
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/remedy
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- collector/launchpad-cve
- source/Launchpad
- collector/nvd-cve
- source/NVD
- collector/nvd-index
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2022-26353
- collector/security-tracker-debian
- source/Debian
- agent/software-canonical-lookup
- collector/usn-cve
- source/Ubuntu
- vendor/qemu
- vendor/debian
- canonical/qemu qemu
- version/qemu qemu/6.2.0
- canonical/debian debian linux
- version/debian debian linux/11.0
- package-manager/debian
- package-manager/ubuntu