CVE-2026-98567

Description

A flaw was found in the Linux kernel. A local privileged user could trigger a Denial of Service (DoS) or kernel memory corruption by causing an out-of-bounds memory write. This issue occurs in the Transmit Packet Steering (XPS) networking mechanism when traffic classes are decreased without clearing leftover entries, allowing out-of-range traffic class indexes to be accessed during queue configuration.

Statement

This vulnerability is rated as having Moderate impact for Red Hat Enterprise Linux because exploitation requires local access and the capability to reconfigure network interface traffic classes and XPS queue mappings. Under default configurations, network queue attributes in sysfs cannot be modified by unprivileged users, restricting exposure to administrative accounts or privileged container environments. While memory corruption can cause a kernel crash and system denial of service, triggering the defect depends on an atypical sequence of decreasing traffic classes followed by reassigning transmit queues.

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)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.