CVE Vulnerabilities

CVE-2022-3534

Use After Free

Published: Oct 17, 2022 | Modified: Nov 07, 2023
CVSS 3.x
8
HIGH
Source:
NVD
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
4.3 LOW
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
Ubuntu
MEDIUM

A vulnerability classified as critical has been found in Linux Kernel. Affected is the function btf_dump_name_dups of the file tools/lib/bpf/btf_dump.c of the component libbpf. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211032.

Weakness

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

Affected Software

Name Vendor Start Version End Version
Linux_kernel Linux - (including) - (including)
Dwarves-dfsg Ubuntu bionic *
Dwarves-dfsg Ubuntu esm-apps/bionic *
Dwarves-dfsg Ubuntu focal *
Dwarves-dfsg Ubuntu trusty *
Dwarves-dfsg Ubuntu xenial *
Libbpf Ubuntu devel *
Libbpf Ubuntu esm-apps/focal *
Libbpf Ubuntu focal *
Libbpf Ubuntu jammy *
Libbpf Ubuntu kinetic *
Libbpf Ubuntu lunar *
Libbpf Ubuntu mantic *
Libbpf Ubuntu noble *
Libbpf Ubuntu oracular *
Libbpf Ubuntu trusty *
Libbpf Ubuntu xenial *

Extended Description

The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system’s reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:

In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Potential Mitigations

References