Answer in brief
CVE-2025-38003 records a Unknown severity vulnerability in can: bcm: add missing rcu read protection for procfs content. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38003 records a Unknown severity vulnerability in can: bcm: add missing rcu read protection for procfs content. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5b48f5711f1c630841ab78dcc061de902f0e37bf <19f553a1ddf260da6570ed8f8d91a8c87f49b63a || >=85cd41070df992d3c0dfd828866fdd243d3b774a <659701c0b954ccdb4a916a4ad59bbc16e726d42c || >=f34f2a18e47b73e48f90a757e1f4aaa8c7d665a1 <0622846db728a5332b917c797c733e202c4620ae || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <6d7d458c41b98a5c1670cbd36f2923c37de51cf5 || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <1f912f8484e9c4396378c39460bbea0af681f319 || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <63567ecd99a24495208dc860d50fb17440043006 || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <7c9db92d5f0eadca30884af75c53d601edc512ee || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <dac5e6249159ac255dad9781793dbe5908ac9ddb || fbac09a3b8890003c0c55294c00709f3ae5501bb || edb4baffb9483141a50fb7f7146cfe4a4c0c2db8 || >=5.4.205 <5.4.294 || >=5.10.130 <5.10.238 || >=5.15.54 <5.15.185 || >=4.19.252 <4.20 || >=5.18.11 <5.19 | 19f553a1ddf260da6570ed8f8d91a8c87f49b63a, 659701c0b954ccdb4a916a4ad59bbc16e726d42c, 0622846db728a5332b917c797c733e202c4620ae, 6d7d458c41b98a5c1670cbd36f2923c37de51cf5, 1f912f8484e9c4396378c39460bbea0af681f319, 63567ecd99a24495208dc860d50fb17440043006, 7c9db92d5f0eadca30884af75c53d601edc512ee, dac5e6249159ac255dad9781793dbe5908ac9ddb, 5.4.294, 5.10.238, 5.15.185, 4.20, 5.19 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jun 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5b48f5711f1c630841ab78dcc061de902f0e37bf <19f553a1ddf260da6570ed8f8d91a8c87f49b63a || >=85cd41070df992d3c0dfd828866fdd243d3b774a <659701c0b954ccdb4a916a4ad59bbc16e726d42c || >=f34f2a18e47b73e48f90a757e1f4aaa8c7d665a1 <0622846db728a5332b917c797c733e202c4620ae || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <6d7d458c41b98a5c1670cbd36f2923c37de51cf5 || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <1f912f8484e9c4396378c39460bbea0af681f319 || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <63567ecd99a24495208dc860d50fb17440043006 || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <7c9db92d5f0eadca30884af75c53d601edc512ee || >=f1b4e32aca0811aa011c76e5d6cf2fa19224b386 <dac5e6249159ac255dad9781793dbe5908ac9ddb || fbac09a3b8890003c0c55294c00709f3ae5501bb || edb4baffb9483141a50fb7f7146cfe4a4c0c2db8 || >=5.4.205 <5.4.294 || >=5.10.130 <5.10.238 || >=5.15.54 <5.15.185 || >=4.19.252 <4.20 || >=5.18.11 <5.19 | 19f553a1ddf260da6570ed8f8d91a8c87f49b63a, 659701c0b954ccdb4a916a4ad59bbc16e726d42c, 0622846db728a5332b917c797c733e202c4620ae, 6d7d458c41b98a5c1670cbd36f2923c37de51cf5, 1f912f8484e9c4396378c39460bbea0af681f319, 63567ecd99a24495208dc860d50fb17440043006, 7c9db92d5f0eadca30884af75c53d601edc512ee, dac5e6249159ac255dad9781793dbe5908ac9ddb, 5.4.294, 5.10.238, 5.15.185, 4.20, 5.19 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jun 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.