CVE-2025-38003
Last modified
CVE-2025-38003 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.19.252, < 4.20 | — |
| Linux | Linux Kernel | >= 5.4.205, < 5.4.294 | — |
| Linux | Linux Kernel | >= 5.10.130, < 5.10.238 | — |
| Linux | Linux Kernel | >= 5.15.54, < 5.15.185 | — |
| Linux | Linux Kernel | >= 5.18.11, < 5.19 | — |
| Linux | Linux Kernel | >= 5.19.1, < 6.1.141 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.93 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.31 | — |
| Linux | Linux Kernel | >= 6.13, < 6.14.9 | — |
| Linux | Linux Kernel | 5.19 | — |
| Linux | Linux Kernel | 6.15 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- 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
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38003?
How severe is CVE-2025-38003?
How do I fix CVE-2025-38003?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-37998In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37999In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3800A vulnerability has been found in WCMS 11 and classified as …9.8
- CVE-2025-38000In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38001In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38002In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38004In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38005In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38006In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38007In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38008In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38009In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38003?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST