CVE Vulnerabilities

CVE-2022-26353

Missing Release of Resource after Effective Lifetime

Published: Mar 16, 2022 | Modified: Feb 12, 2023
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
Ubuntu
LOW

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.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

Name Vendor Start Version End Version
Qemu Qemu 6.2.0 (including) 6.2.0 (including)
Advanced Virtualization for RHEL 8.4.0.EUS RedHat virt:av-8040020220517095834.522a0ee4 *
Advanced Virtualization for RHEL 8.4.0.EUS RedHat virt-devel:av-8040020220517095834.522a0ee4 *
Red Hat Enterprise Linux 8 RedHat virt-devel:rhel-8060020220616155742.ad008a3a *
Red Hat Enterprise Linux 8 RedHat virt:rhel-8060020220616155742.ad008a3a *
Red Hat Enterprise Linux 9 RedHat qemu-kvm-17:6.2.0-11.el9_0.3 *
Qemu Ubuntu bionic *
Qemu Ubuntu devel *
Qemu Ubuntu esm-infra/bionic *
Qemu Ubuntu focal *
Qemu Ubuntu impish *
Qemu Ubuntu jammy *
Qemu Ubuntu kinetic *
Qemu Ubuntu lunar *
Qemu Ubuntu mantic *
Qemu Ubuntu noble *
Qemu Ubuntu trusty *
Qemu Ubuntu xenial *

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References