CVE-2021-47419

Description

A flaw was found in the Linux kernel's Time-Aware Priority (TAPRIO) network scheduling module. This vulnerability allows a local attacker with network configuration privileges to cause a Denial of Service (DoS) by crashing the system. When a TAPRIO queuing discipline is dismantled, the kernel fails to properly cancel an active timer, leading to memory corruption when the active object is freed.

Statement

This vulnerability is evaluated with a Low severity impact because triggering it requires local administrative privileges, specifically CAP_NET_ADMIN, to manipulate traffic control queueing disciplines. The Time-Aware Priority scheduler is not utilized by default and is typically deployed only in specialized Time-Sensitive Networking environments. As a result, successful exploitation is restricted to privileged local users and results solely in a denial of service through a system crash.

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.15.57.8
Attack VectorLocalLocalLocal
Attack ComplexityHighLowLow
Privileges RequiredHighLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneHigh
Integrity ImpactNoneNoneHigh
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/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: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)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart

Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.