CVE-2022-48916

Description

A flaw was found in the Linux kernel's Intel IOMMU (Input-Output Memory Management Unit) driver. When enabling Intel Volume Management Device (VMD) in scalable mode, an initialization error fails to properly clean up device information tables. This failure leads to a duplicate list insertion during subsequent device registration, triggering a kernel panic. A local user could exploit this flaw to crash the system, resulting in a Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate impact because successful exploitation requires specific platform hardware configurations and results in a local denial of service through a system crash without compromising confidentiality or integrity. The issue only manifests on systems equipped with Intel Volume Management Device (VMD) controllers operating under IOMMU scalable mode during device initialization. Typical enterprise deployments not employing VMD NVMe aggregation or scalable mode are not exposed to this failure condition.

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 Score5.55.5N/A
Attack VectorLocalLocalN/A
Attack ComplexityLowLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityNoneNoneN/A
Integrity ImpactNoneNoneN/A
Availability ImpactHighHighN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/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:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity,Confidentiality

Technical Impact: Modify Application Data; Read Application Data

If a released resource is subsequently reused or reallocated, then an attempt to use the original resource might allow access to sensitive data that is associated with a different user or entity.

Other,Availability

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

When a resource is released it might not be in an expected state, later attempts to access the resource may lead to resultant errors that may lead to a crash.

Frequently Asked Questions

Want to get errata notifications? Sign up here.