CVE-2026-99401

Description

A flaw was found in the Linux kernel's rtnetlink subsystem. A missing synchronization step in rtnl_link_unregister() creates a race condition where network link operation structures can be accessed after their backing kernel module has been unloaded. A local user could exploit this flaw by requesting interface information while a network module is being removed, causing memory corruption and a Denial of Service (DoS) through a system crash.

Statement

This vulnerability is classified as Moderate severity for Red Hat enterprise products because exploitation requires local access and precise timing during administrative kernel module unloading to trigger the race condition. Although any local unprivileged user can issue rtnetlink queries, module unloading generally necessitates administrative privileges or explicit maintenance procedures, which significantly limits practical attack opportunities. Furthermore, the maximum impact is restricted to a local denial of service through a kernel panic, without confidentiality or integrity compromise.

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.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/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:H/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.