CVE-2025-38004: can: bcm: add locking for bcm_op runtime updates

Severity: high (CVSS 7.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-06-08 · updated 2026-10-15
Weakness: CWE-125

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be prevented with a spin_lock_bh. At the rework of bcm_can_tx() the 'count' variable has been moved into the protected section as this variable can be modified from both contexts too.

Affected products

Debian Linux: 11.0
Linux kernel: from 2.6.25 before 5.4.294; from 5.5 before 5.10.238; from 5.11 before 5.15.185; from 5.16 before 6.1.141; from 6.2 before 6.6.93; from 6.7 before 6.12.31 — fixed in 5.10.238, 5.15.185, 5.4.294, 6.1.141, 6.12.31, 6.14.9

How to fix

Upgrade to a fixed version: Linux kernel 5.10.238, 5.15.185, 5.4.294, 6.1.141. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-38004 or the next vulnerability affects your stack