CVE-2026-98503

Description

A flaw was found in the Linux kernel's packet socket implementation. A local user can cause a Denial of Service (DoS) or system instability by triggering premature reuse of transmit ring buffer slots while packet data is still in flight. Because these shared memory slots may be released and reused before transmission is finished, the kernel can experience memory corruption leading to an unexpected crash.

Statement

This vulnerability is rated as Moderate because exploitation is restricted to local attackers and primarily leads to a denial of service through a system crash. In standard Red Hat Enterprise Linux configurations, interacting with raw packet transmission rings requires the CAP_NET_RAW capability or unprivileged user namespaces. As a result, the blast radius is limited to disrupting kernel availability without granting arbitrary code execution or unauthorized data access.

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 Application Data; Read Memory

If the released resource is subsequently reused or reallocated, then a read operation on the original resource might access sensitive data that is associated with a different user or entity.

Availability

Technical Impact: Unexpected State; DoS: Crash, Exit, or Restart

When the resource is released, the software might modify some of its structure, or close associated channels (such as a file descriptor). When the software later accesses the resource as if it is valid, the resource might not be in an expected state, leading to resultant errors that may lead to a crash.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands; Modify Application Data; Modify Memory

When the resource is released, the software might modify some of its structure. This might affect logic in the sections of code that still assume the resource is active. If the released resource is related to memory and is used in a function call, or points to unexpected data in a write operation, then code execution may be possible upon subsequent accesses.

Frequently Asked Questions

Want to get errata notifications? Sign up here.