CVE-2022-50508

Description

A flaw was found in the Linux kernel's MediaTek mt76 wireless driver. An adjacent wireless or local attacker can trigger an out-of-bounds memory read during transmission power calculations in the mt76x0_phy_get_target_power routine. This vulnerability could lead to a kernel crash, resulting in a Denial of Service (DoS), or potentially expose sensitive memory contents.

Statement

This vulnerability is rated as having Moderate impact because exploitation is constrained to systems utilizing specific MediaTek wireless hardware and requires local or adjacent wireless access to trigger an out-of-bounds memory read, potentially causing a kernel crash or limited information exposure. Red Hat Enterprise Linux is not affected by this flaw because the flawed driver logic was introduced in later upstream kernels and was never incorporated into supported Red Hat kernel builds.

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 HatNVDcve.org
Base Score6.57.17.1
Attack VectorLocalLocalAdjacent Network
Attack ComplexityHighLowLow
Privileges RequiredLowLowNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityLowHighLow
Integrity ImpactHighNoneNone
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H

NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.