CVE Vulnerabilities

CVE-2022-26365

Missing Release of Memory after Effective Lifetime

Published: Jul 05, 2022 | Modified: Nov 07, 2023
CVSS 3.x
7.1
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CVSS 2.x
3.6 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu

Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends dont zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740). Additionally the granularity of the grant table doesnt allow sharing less than a 4K page, leading to unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend (CVE-2022-33741, CVE-2022-33742).

Weakness

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

Affected Software

Name Vendor Start Version End Version
Linux_kernel Linux 2.6.13 (including) 4.9.322 (excluding)
Linux_kernel Linux 4.14 (including) 4.14.287 (excluding)
Linux_kernel Linux 4.19 (including) 4.19.251 (excluding)
Linux_kernel Linux 5.4 (including) 5.4.204 (excluding)
Linux_kernel Linux 5.10 (including) 5.10.129 (excluding)
Linux_kernel Linux 5.15 (including) 5.15.53 (excluding)
Linux_kernel Linux 5.18 (including) 5.18.10 (excluding)
Linux_kernel Linux 2.6.12-rc2 (including) 2.6.12-rc2 (including)
Linux_kernel Linux 2.6.12-rc3 (including) 2.6.12-rc3 (including)
Linux_kernel Linux 2.6.12-rc4 (including) 2.6.12-rc4 (including)
Linux_kernel Linux 2.6.12-rc5 (including) 2.6.12-rc5 (including)
Linux_kernel Linux 2.6.12-rc6 (including) 2.6.12-rc6 (including)
Linux_kernel Linux 5.19-rc1 (including) 5.19-rc1 (including)
Linux_kernel Linux 5.19-rc2 (including) 5.19-rc2 (including)
Linux_kernel Linux 5.19-rc3 (including) 5.19-rc3 (including)
Linux_kernel Linux 5.19-rc4 (including) 5.19-rc4 (including)
Linux_kernel Linux 5.19-rc5 (including) 5.19-rc5 (including)
Xen Xen - (including) - (including)

Potential Mitigations

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
  • For example, glibc in Linux provides protection against free of invalid pointers.
  • When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
  • To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References