CVE-2022-26353

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.18%
Vendor Advisory debian.org Vendor Advisory gentoo.org Vendor Advisory nongnu.org
Affected: n/a qemu-kvm
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2022-26353?
CVE-2022-26353 has been scored as a high severity vulnerability.
How to fix CVE-2022-26353?
To fix CVE-2022-26353, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-26353 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-26353 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-26353?
CVE-2022-26353 affects n/a qemu-kvm.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.