CVE-2026-99674

Description

A flaw was found in the Linux kernel's Controller Area Network (CAN) subsystem. A local user capable of transmitting raw network packets can trigger a buffer overflow by sending CAN Extra Long (CAN XL) frames to a network device that does not support them. Because the kernel fails to validate device capabilities before processing, non-supported drivers misinterpret frame header flags as data length, leading to memory corruption, a Denial of Service (DoS), or potential privilege escalation.

Statement

This vulnerability is rated as Moderate impact because exploitation requires local access with privileged raw socket permissions (such as CAP_NET_RAW) and is contingent on active non-CAN XL network devices. Controller Area Network (CAN) interfaces are rarely configured or deployed in standard enterprise environments, which substantially limits the attack surface. Although a local privileged attacker could induce kernel memory corruption by transmitting specially crafted raw frames, the flaw cannot be triggered over standard network interfaces or without elevated privileges.

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 Score6.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

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