CVE-2022-50335

Description

A flaw was found in the Linux kernel's 9P network protocol client. When allocating a new request structure, its reference count is not initialized before the request is registered for incoming responses. An authenticated local user could exploit this race condition during concurrent filesystem operations to cause improper memory reuse. This flaw primarily results in a Denial of Service (DoS) through a system crash or memory corruption.

Statement

This vulnerability is rated Moderate severity because exploiting the race condition in the 9P network protocol client requires local access and precise timing during active 9P operations, limiting the realistic attack surface. Plan 9 (9P) file systems are not mounted by default in standard Red Hat Enterprise Linux environments, requiring specific workloads such as virtualization guest sharing to expose the interface. Successful exploitation requires an authenticated local user capable of triggering concurrent filesystem requests, resulting in potential denial of service or memory corruption rather than direct remote compromise.

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 Score75.59.8
Attack VectorLocalLocalNetwork
Attack ComplexityHighLowLow
Privileges RequiredLowLowNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityHighNoneHigh
Integrity ImpactHighNoneHigh
Availability ImpactHighHighHigh

Vector

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

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.