CVE-2025-38003: Linux kernel · can: bcm: add missing rcu read protection for procfs content
Affects Linux kernelSource CVE Database V5
Not known to be exploited.
Data as of 26 Oct 2026, 09:15 UTC
Rated High by the CNA (Linux) · No CVSS score from NVD or the CNA
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2025-38003, European organizations should prioritize updating their Linux kernel to the patched versions that include the fix for the missing RCU read protection in the bcm CAN driver. Kernel updates should be tested in staging environments to ensure compatibility with existing applications and hardware. Organizations using custom or embedded Linux distributions should coordinate with vendors or maintainers to integrate the patch promptly. Additionally, system administrators should audit systems that utilize the CAN subsystem, particularly in automotive or industrial contexts, to identify vulnerable kernel versions. Employing kernel hardening techniques such as Kernel Address Space Layout Randomization (KASLR), Kernel Page Table Isolation (KPTI), and enabling security modules like SELinux or AppArmor can reduce the risk of exploitation. Monitoring kernel logs and procfs outputs for anomalies may help detect attempts to exploit the vulnerability. Finally, restricting local user access and minimizing unnecessary privileges can limit the attack surface, as exploitation likely requires local access to the system.
Description
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu read protection for procfs content When the procfs content is generated for a bcm_op which is in the process to be removed the procfs output might show unreliable data (UAF). As the removal of bcm_op's is already implemented with rcu handling this patch adds the missing rcu_read_lock() and makes sure the list entries are properly removed under rcu protection.
References
- git.kernel.org/stable/c/19f553a1ddf260da6570ed8f8d91a8c87f49b63a (opens in a new tab)
- git.kernel.org/stable/c/659701c0b954ccdb4a916a4ad59bbc16e726d42c (opens in a new tab)
- git.kernel.org/stable/c/0622846db728a5332b917c797c733e202c4620ae (opens in a new tab)
- git.kernel.org/stable/c/6d7d458c41b98a5c1670cbd36f2923c37de51cf5 (opens in a new tab)
- git.kernel.org/stable/c/1f912f8484e9c4396378c39460bbea0af681f319 (opens in a new tab)
- git.kernel.org/stable/c/63567ecd99a24495208dc860d50fb17440043006 (opens in a new tab)
- git.kernel.org/stable/c/7c9db92d5f0eadca30884af75c53d601edc512ee (opens in a new tab)
- git.kernel.org/stable/c/dac5e6249159ac255dad9781793dbe5908ac9ddb (opens in a new tab)