CVE-2022-49176

Description

A flaw was found in the Linux kernel's BFQ (Budget Fair Queueing) storage scheduler. During request processing, the scheduler may continue to read data from a queue structure that has already been released from memory, leading to a use-after-free condition. A local user could exploit this flaw by issuing specific storage input/output (I/O) operations on a system utilizing the BFQ scheduler, causing a system crash and resulting in a denial of service (DoS).

Statement

This vulnerability is rated as having Moderate impact for Red Hat Enterprise Linux because exploitation is restricted to local access and requires the BFQ I/O scheduler to be explicitly active on the target block device. On typical Red Hat Enterprise Linux installations, alternate schedulers such as mq-deadline or none are commonly selected by default, limiting overall exposure. If BFQ is actively used, local users generating specific block I/O traffic could trigger this memory access flaw, resulting in a kernel crash and local denial of service.

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.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.