CVE-2022-50283

Description

A flaw was found in the Linux kernel's Memory Technology Device (MTD) subsystem, which manages flash storage devices. Due to a missing reference count update in the dynamic partition handling code, memory representing device nodes can be released prematurely. A local attacker can trigger this issue during device configuration, leading to memory corruption and a Denial of Service (DoS) via a system crash.

Statement

This flaw is rated as having Moderate impact for Red Hat because exploitation is restricted to local system initialization on platforms with specific device-tree hardware, posing a denial of service risk rather than broad remote compromise. Enterprise environments typically run on standard server architectures that do not utilize Memory Technology Device (MTD) dynamic partitioning. Additionally, supported Red Hat Enterprise Linux releases do not include the upstream kernel changes that introduced this reference counting defect.

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 Score4.47.87.8
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredHighLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneHighHigh
Integrity ImpactNoneHighHigh
Availability ImpactHighHighHigh

Vector

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

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

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

Understanding the Weakness (CWE)

Other

Technical Impact: Quality Degradation; Varies by Context

The use of inconsistent implementations can cause changes in behavior when the code is ported or built under a different environment than the programmer expects, which can lead to security problems in some cases.

Frequently Asked Questions

Want to get errata notifications? Sign up here.