CVE-2026-72118

Technical Description

In the Linux kernel, the following vulnerability has been resolved:

can: bcm: fix CAN frame rx/tx statistics

KCSAN detected a data race within the bcm_rx_handler() when two CAN frames

have been simultaneously received and processed in a single rx op by two

different CPUs.

Use atomic operations with (signed) long data types to access the

statistics in the hot path to fix the KCSAN complaint.

Additionally simplify the update and check of statistics overflow by

using the atomic operations in separate bcm_update_[rx|tx]_stats()

functions. The rx variant runs under bcm_rx_update_lock to prevent

races when resetting the two rx counters; the tx variant runs under

bcm_tx_lock and only needs to guard its own counter's overflow.

As the rx path resets its values already at LONG_MAX / 100, there is

no conflict between the two locking domains (bcm_rx_update_lock vs.

bcm_tx_lock) even for ops that use both paths.

The rx statistics update and the frames_filtered update in

bcm_rx_changed() were

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References