216.73.217.98

CVE-2025-38004

· Published 08/06/2025 11:15 · Modified 09/06/2025 12:15

Labels: CVE-2025-38004 2025-06-08416baaa9-dc9f-4396-8d5f-8c081fb06d67CVE-2025-38004

Essential information

Published
08/06/2025 11:15
Modified
09/06/2025 12:15
Author
Creator
CISA KEV
No
CWE

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.

NVD status

Status
Awaiting Analysis — CVE has been recently published to the CVE List and has been received by the NVD.
Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD
View on NVD

Affected products (CPE)

ProductCPE
linux / linux kernel cpe:2.3:a:linux:linux_kernel:*:*:*:*:*:*:*:*
linux / can bcm cpe:2.3:a:linux:can_bcm:*:*:*:*:*:*:*:*

References