Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38004can: bcm: add locking for bcm_op runtime updates

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38004, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 80% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 8f1c022541bf5a923c8d6fa483112c15250f30a4
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 7595de7bc56e0e52b74e56c90f7e247bf626d628
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < fbd8fdc2b218e979cfe422b139b8f74c12419d1f
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 2a437b86ac5a9893c902f30ef66815bf13587bf6
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 76c84c3728178b2d38d5604e399dfe8b0752645e
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < cc55dd28c20a6611e30596019b3b2f636819a4c0
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7
  • Linux · Linux

    • affected 2.6.25
    • unaffected < 2.6.25
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.185 – ≤ 5.15.*
    • unaffected 6.1.141 – ≤ 6.1.*
    • unaffected 6.6.93 – ≤ 6.6.*
    • unaffected 6.12.31 – ≤ 6.12.*
    • unaffected 6.14.9 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38004 badge
[![CVE-2025-38004](https://cveledger.app/badge/CVE-2025-38004.svg)](https://cveledger.app/cve/CVE-2025-38004)

Record last updated .