Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2a437b86ac5a9893c902f30ef66815bf13587bf6, 7595de7bc56e0e52b74e56c90f7e247bf626d628, 76c84c3728178b2d38d5604e399dfe8b0752645e.

Low priority for now. Upgrade to Linux Linux 2a437b86ac5a9893c902f30ef66815bf13587bf6, 7595de7bc56e0e52b74e56c90f7e247bf626d628, 76c84c3728178b2d38d5604e399dfe8b0752645e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 8, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.1
CNA · Linux
7.3
0.2 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38004

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.238
  • linux linux kernel5.11 and later · before 5.15.185
  • linux linux kernel5.16 and later · before 6.1.141
  • linux linux kernel2.6.25 and later · before 5.4.294
  • linux linux kernel6.7 and later · before 6.12.31
  • linux linux kernel6.13 and later · before 6.14.9
  • linux linux kernel6.2 and later · before 6.6.93
  • linux linux kernel6.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.25affected
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 8f1c022541bf5a923c8d6fa483112c15250f30a4affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 7595de7bc56e0e52b74e56c90f7e247bf626d628affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before fbd8fdc2b218e979cfe422b139b8f74c12419d1faffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 2a437b86ac5a9893c902f30ef66815bf13587bf6affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 76c84c3728178b2d38d5604e399dfe8b0752645eaffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before cc55dd28c20a6611e30596019b3b2f636819a4c0affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before c4e8a172501e677ebd8ea9d9161d97dc4df56fbdaffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7affected · git
    • before 2.6.25not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-develbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-cross-headersbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-debug-develbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.45.1.el9_85.14.0-687.45.1.el9_8

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38001Jun 6, 2025 · net_sched: hfsc: Address reentrant enqueue adding class to eltree twice
    22Monitor
  • ← EarlierCVE-2025-38003Jun 8, 2025 · can: bcm: add missing rcu read protection for procfs content
    22Monitor
  • Later →CVE-2025-38005Jun 18, 2025 · dmaengine: ti: k3-udma: Add missing locking
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2a437b86ac5a9893c902f30ef66815bf13587bf6Vendor (CNA)
Linux Linux7595de7bc56e0e52b74e56c90f7e247bf626d628Vendor (CNA)
Linux Linux76c84c3728178b2d38d5604e399dfe8b0752645eVendor (CNA)
Linux Linux8f1c022541bf5a923c8d6fa483112c15250f30a4Vendor (CNA)
Linux Linuxc2aba69d0c36a496ab4f2e81e9c2b271f2693fd7Vendor (CNA)
Linux Linuxc4e8a172501e677ebd8ea9d9161d97dc4df56fbdVendor (CNA)
Linux Linuxcc55dd28c20a6611e30596019b3b2f636819a4c0Vendor (CNA)
Linux Linuxfbd8fdc2b218e979cfe422b139b8f74c12419d1fVendor (CNA)
almalinux:kernel5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.45.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.147-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records