CVE Catalog

CVE-2025-38004

HighCVSS 7.3
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.21%

11th percentile - higher than 11% of all known CVEs

Summary

In the CAN broadcast manager (BCM) of the Linux kernel, a missing locking for runtime updates was found. The currframe counter and count variable could be modified concurrently from user space and timer context, leading to out-of-bounds buffer read.

Risk Assessment

The bug can cause system crashes (kernel panic) or unpredictable behavior of CAN applications during dynamic frame sequence changes.

Recommendation

Update the Linux kernel to a version containing the fix adding spin_lock_bh in critical sections.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS