Answer in brief
CVE-2025-38004 records a Unknown severity vulnerability in can: bcm: add locking for bcm_op runtime updates. 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-38004 records a Unknown severity vulnerability in can: bcm: add locking for bcm_op runtime updates. 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 | >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <8f1c022541bf5a923c8d6fa483112c15250f30a4 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <7595de7bc56e0e52b74e56c90f7e247bf626d628 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <fbd8fdc2b218e979cfe422b139b8f74c12419d1f || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <2a437b86ac5a9893c902f30ef66815bf13587bf6 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <76c84c3728178b2d38d5604e399dfe8b0752645e || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <cc55dd28c20a6611e30596019b3b2f636819a4c0 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <c4e8a172501e677ebd8ea9d9161d97dc4df56fbd || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 | 8f1c022541bf5a923c8d6fa483112c15250f30a4, 7595de7bc56e0e52b74e56c90f7e247bf626d628, fbd8fdc2b218e979cfe422b139b8f74c12419d1f, 2a437b86ac5a9893c902f30ef66815bf13587bf6, 76c84c3728178b2d38d5604e399dfe8b0752645e, cc55dd28c20a6611e30596019b3b2f636819a4c0, c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 |
| Linux/Linuxgeneric | 2.6.25 | 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 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.
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 | >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <8f1c022541bf5a923c8d6fa483112c15250f30a4 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <7595de7bc56e0e52b74e56c90f7e247bf626d628 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <fbd8fdc2b218e979cfe422b139b8f74c12419d1f || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <2a437b86ac5a9893c902f30ef66815bf13587bf6 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <76c84c3728178b2d38d5604e399dfe8b0752645e || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <cc55dd28c20a6611e30596019b3b2f636819a4c0 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <c4e8a172501e677ebd8ea9d9161d97dc4df56fbd || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 | 8f1c022541bf5a923c8d6fa483112c15250f30a4, 7595de7bc56e0e52b74e56c90f7e247bf626d628, fbd8fdc2b218e979cfe422b139b8f74c12419d1f, 2a437b86ac5a9893c902f30ef66815bf13587bf6, 76c84c3728178b2d38d5604e399dfe8b0752645e, cc55dd28c20a6611e30596019b3b2f636819a4c0, c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 |
| Linux/Linuxgeneric | 2.6.25 | 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 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.
Quoted source text, attributed separately from HOL analysis.