CVE-2026-99671

Description

A flaw was found in the Linux kernel's CAN (Controller Area Network) subsystem. A local attacker can cause a Denial of Service (DoS) by stalling memory copies between user space and the kernel when configuring CAN socket options. Because internal socket locks are held throughout these operations, a stalled memory transfer can block core network management tasks and result in system hangs or deadlocks.

Statement

This vulnerability is rated as Moderate severity because exploitation requires local access and is restricted to causing a denial of service, with no impact on data confidentiality or system integrity. In standard Red Hat Enterprise Linux environments, Controller Area Network (CAN) protocols are rarely enabled or utilized, limiting real-world exposure primarily to systems configured for automotive or industrial bus communication. A local authenticated attacker could cause socket option copies to stall, leading to blocked networking subsystem locks and disrupting device management operations.

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)

Availability

Technical Impact: DoS: Resource Consumption (Other)

When an attacker can control a lock, the program may wait indefinitely until the attacker releases the lock, causing a denial of service to other users of the program. This is especially problematic if there is a blocking operation on the lock.

Frequently Asked Questions

Want to get errata notifications? Sign up here.