CVE-2026-72119
Received Received - Intake

CAN BCM Frame Validation Race Condition

Vulnerability report for CVE-2026-72119, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-15

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcm_tx_lock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc()'d buffer and validate it there, mirroring the approach already used in bcm_rx_setup(). Only copy the validated data into op->frames while holding op->bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler() can no longer observe a partially updated or unvalidated frame. Add a missing error path for memcpy_from_msg() when copying CAN frame data from userspace. Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup() under op->bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the torn 64-bit ktime_t read on 32-bit platforms.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-15
Generated
2026-08-15
AI Q&A
2026-08-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a race condition in the CAN BCM protocol implementation. It allows for potential corruption of CAN frame data during transmission by not properly synchronizing updates between the kernel and userspace. The issue arises when frame data is staged in a temporary buffer without proper locking, leading to possible inconsistencies.

Detection Guidance

This vulnerability is specific to the Linux kernel's CAN bus module (bcm). Detection requires checking kernel logs for CAN-related errors or kernel panics. Commands like dmesg | grep -i can or journalctl -k | grep -i can may help identify issues. Ensure your kernel version is updated to a patched release.

Impact Analysis

This vulnerability could allow an attacker with local access to corrupt CAN frame data, potentially causing system instability or unexpected behavior in applications relying on CAN communication. It may lead to data corruption or denial of service in systems using CAN protocols.

Mitigation Strategies

Update your Linux kernel to the latest stable version that includes the fix for this vulnerability. If immediate patching is not possible, consider disabling the CAN BCM module via kernel parameters (e.g., blacklisting the can-bcm module) as a temporary workaround.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72119. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart