CVE-2025-38004
Published Jun 8, 2025
Last updated a month ago
- 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.
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- NVD status
- Awaiting Analysis
- Hype score
- Not currently trending
Latest CVE analysis: CVE-2025-38004 maintains presence, while new exploits emerge, impacting Android security landscape. More details: https://t.co/tej1yYFNGt Created by AI. #Android #Cybersecurity
@Funker_Dev
17 Jul 2025
9 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
CVE-2025-38004 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 … https://t.co/aZyAfp0s92
@CVEnew
8 Jun 2025
603 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes