CVE-2025-38004
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 7.3 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Modified
Affected
- Linux Kernel < 5.4.294
- Linux Kernel < 5.10.238
- Linux Kernel < 5.15.185
- Linux Kernel < 6.1.141
- Linux Kernel < 6.6.93
- Linux Kernel < 6.12.31
- Linux Kernel < 6.14.9
- Linux Kernel 6.15
Attack profile CVSS 3.1 · 7.3
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38004.md and follow it. Check whether this project is affected by CVE-2025-38004. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2a437b86ac5a9893c902f30ef66815bf13587bf6
- https://git.kernel.org/stable/c/7595de7bc56e0e52b74e56c90f7e247bf626d628
- https://git.kernel.org/stable/c/76c84c3728178b2d38d5604e399dfe8b0752645e
- https://git.kernel.org/stable/c/8f1c022541bf5a923c8d6fa483112c15250f30a4
- https://git.kernel.org/stable/c/c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7
- https://git.kernel.org/stable/c/c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
- https://git.kernel.org/stable/c/cc55dd28c20a6611e30596019b3b2f636819a4c0
- https://git.kernel.org/stable/c/fbd8fdc2b218e979cfe422b139b8f74c12419d1f
References
- https://git.kernel.org/stable/c/2a437b86ac5a9893c902f30ef66815bf13587bf6
- https://git.kernel.org/stable/c/7595de7bc56e0e52b74e56c90f7e247bf626d628
- https://git.kernel.org/stable/c/76c84c3728178b2d38d5604e399dfe8b0752645e
- https://git.kernel.org/stable/c/8f1c022541bf5a923c8d6fa483112c15250f30a4
- https://git.kernel.org/stable/c/c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7
- https://git.kernel.org/stable/c/c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
- https://git.kernel.org/stable/c/cc55dd28c20a6611e30596019b3b2f636819a4c0
- https://git.kernel.org/stable/c/fbd8fdc2b218e979cfe422b139b8f74c12419d1f
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html