CVE-2026-99688

Description

A flaw was found in the Linux kernel's Quick Fair Queueing (QFQ) network packet scheduler. A local user could exploit a race condition during traffic class reconfiguration to cause a Denial of Service (DoS) or potentially execute arbitrary code. A locking gap permits concurrent queue operations to free and subsequently access an aggregate memory structure, resulting in a use-after-free condition.

Statement

This vulnerability is rated as Moderate because exploitation is restricted to local environments and requires elevated privileges, such as CAP_NET_ADMIN, to manipulate traffic control scheduling. The sch_qfq kernel module is not loaded by default on Red Hat Enterprise Linux systems and is only utilized when explicitly configured for traffic management. Consequently, standard production installations that do not employ this specific queueing discipline remain unaffected unless an attacker already possesses the privileges needed to load and configure network schedulers.

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/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.