CVE-2025-38004can: bcm: add locking for bcm_op runtime updates
Updated under an hour ago ()
Does this affect you?
It affects Linux and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.3 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 8f1c022541bf5a923c8d6fa483112c15250f30a4; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 7595de7bc56e0e52b74e56c90f7e247bf626d628; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before fbd8fdc2b218e979cfe422b139b8f74c12419d1f; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 2a437b86ac5a9893c902f30ef66815bf13587bf6; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 76c84c3728178b2d38d5604e399dfe8b0752645e; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before cc55dd28c20a6611e30596019b3b2f636819a4c0; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before c4e8a172501e677ebd8ea9d9161d97dc4df56fbd; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 | CNA record |
linux linux_kernel linux: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; from 6.13 before 6.14.9; 6.15; and 6 more ranges | NVD |
debian debian_linux debian:debian_linux | 11.0 | NVD |
References
- https://git.kernel.org/stable/c/8f1c022541bf5a923c8d6fa483112c15250f30a4patch
- https://git.kernel.org/stable/c/7595de7bc56e0e52b74e56c90f7e247bf626d628patch
- https://git.kernel.org/stable/c/fbd8fdc2b218e979cfe422b139b8f74c12419d1fpatch
- https://git.kernel.org/stable/c/2a437b86ac5a9893c902f30ef66815bf13587bf6patch
- https://git.kernel.org/stable/c/76c84c3728178b2d38d5604e399dfe8b0752645epatch
- https://git.kernel.org/stable/c/cc55dd28c20a6611e30596019b3b2f636819a4c0patch
- https://git.kernel.org/stable/c/c4e8a172501e677ebd8ea9d9161d97dc4df56fbdpatch
- https://git.kernel.org/stable/c/c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7patch
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlthird-party-advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.