Review reviewHigh

CVE-2025-38004

Linux Linux, linux kernel, debian linux

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 pr...

CVSS
7.1
EPSS
0.21%
10.7% percentile
CISA KEV
Not listed
Published
2025.06.08
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.21%
Technical severityCVSS 7.1

Vulnerability overview

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 pr...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 8f1c022541bf5a923c8d6fa483112c15250f30a4, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 7595de7bc56e0e52b74e56c90f7e247bf626d628, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < fbd8fdc2b218e979cfe422b139b8f74c12419d1f, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 2a437b86ac5a9893c902f30ef66815bf13587bf6, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 76c84c3728178b2d38d5604e399dfe8b0752645e, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < cc55dd28c20a6611e30596019b3b2f636819a4c0, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, >= 2.6.25, >= 2.6.25 < 5.4.294, >= 5.5 < 5.10.238, >= 5.11 < 5.15.185, >= 5.16 < 6.1.141, >= 6.2 < 6.6.93, >= 6.7 < 6.12.31, >= 6.13 < 6.14.9, 6.15, 11.0
Fixed versions
5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 6.14.9

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CWE
CWE-125