CVE-2022-50665
Description
A flaw was found in the Linux kernel's ath11k wireless driver. When performing wireless network scans while disconnected from an access point, the driver fails to properly reinitialize internal peer identification data structures after clearing memory. This condition can lead to driver errors, kernel warnings, and potential operational disruption resulting in a Denial of Service (DoS).
Statement
Red Hat has evaluated this vulnerability as having a Low impact because it strictly affects systems equipped with Qualcomm ath11k wireless network adapters. Typical Red Hat Enterprise Linux enterprise server environments do not use this wireless hardware and remain unaffected. Even on systems where the driver is active, the issue is limited to improper peer descriptor handling during disconnected Wi-Fi scanning, presenting a minor operational disruption without compromising system confidentiality or integrity.
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 | 2.5 | N/A | 7.1 |
| Attack Vector | Local | N/A | Adjacent Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | Low |
| Availability Impact | Low | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
The resource might be left in an unexpected state when it is accessed or used.
Confidentiality
Technical Impact: Read Memory; Read Application Data
When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.
Access Control
Technical Impact: Bypass Protection Mechanism
If security-critical decisions rely on a variable having a "0" or equivalent value, and the programming language performs this initialization on behalf of the programmer, then a bypass of security may occur.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The uninitialized data may contain values that cause program flow to change in ways that the programmer did not intend. For example, if an uninitialized variable is used as an array index in C, then its previous contents may produce an index that is outside the range of the array, possibly causing a crash or an exit in other environments.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.