CVE-2022-50259
Description
A flaw was found in the Linux kernel. A local user could exploit a race condition in the sock_map_free() function, which incorrectly calls release_sock(sk) without holding a proper reference to the socket. This can lead to a use-after-free vulnerability, potentially causing a system crash and resulting in a Denial of Service (DoS).
Statement
A use-after-free flaw was found in the Linux kernel's BPF sockmap implementation. The sock_map_free() function calls release_sock(sk) without owning a reference on the socket, so a local user able to create and tear down BPF sockmaps can trigger a race condition that causes a use-after-free and a system crash, resulting in a denial of service. Red Hat rates the impact of this issue as Low because exploitation requires local access with high privileges, the race condition is difficult to win, and the demonstrated impact is limited to system availability. This differs from the upstream CVE record, which assigns a higher severity (7.8, including high confidentiality and integrity impact); the available technical evidence, including the syzbot report, shows only an availability impact from the use-after-free and no indication of confidentiality or integrity impact. Red Hat Enterprise Linux 8 and 9, including the kernel-rt variant, are affected. The fix is currently deferred on the affected streams: given the low severity, the high privileges required, and the narrow timing window of the race, a fix will be delivered in a future planned update rather than as an urgent out-of-band fix. The residual risk is that a highly privileged local attacker able to use BPF sockmaps could crash the system, causing a denial of service. Red Hat Enterprise Linux 6, 7, and 10, and Red Hat In-Vehicle OS are not affected because the vulnerable code is not present in those products.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.1 | 4.7 | 7.8 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | High | High | Low |
| Privileges Required | High | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | None | High |
| Integrity Impact | None | None | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.