LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38003: can: bcm: add missing rcu read protection for procfs content

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel race can expose already-freed memory while procfs reports CAN Broadcast Manager operations being removed. The CVSS assessment indicates a local, low-privilege attacker could potentially cause serious confidentiality, integrity, or availability impact, although the supplied description only confirms unreliable output and a use-after-free condition.

Executive priority

Treat this as a high-priority kernel update for systems with untrusted local access or CAN workloads. It is not presented as an internet-remote issue, and active exploitation is unconfirmed. Use normal expedited patching rather than emergency incident measures unless internal evidence indicates abuse.

Technical view

CVE-2025-38003 is a use-after-free race in Linux CAN BCM procfs generation. A bcm_op may be removed while its data is being read for procfs output. The fix adds missing RCU read-side protection and ensures list entries are removed under RCU protection.

Likely exposure

Exposure is limited to Linux systems within affected kernel branches where CAN BCM procfs activity is reachable. The supplied version data mixes release numbers and commit identifiers and is insufficient for reliable comparison alone. Confirm status against the running distribution kernel and its backport guidance.

Exploitation context

The CVSS vector indicates local access, low privileges, low complexity, and no user interaction. The bundle marks this CVE as absent from KEV, and no supplied source establishes active exploitation or a public exploit. Practical exploitability beyond unreliable procfs data is not demonstrated here.

Researcher notes

The confirmed defect is missing RCU read protection during concurrent procfs traversal and bcm_op removal. The fix addresses reader lifetime and RCU-safe list deletion. Although CVSS assigns high impact across confidentiality, integrity, and availability, the description does not demonstrate privilege escalation, code execution, or a reliable exploitation outcome.

Mitigation direction

  • Install a vendor-supported kernel containing the referenced RCU protection fix.
  • Reboot into the updated kernel after installation.
  • Check distribution guidance when kernel backports make version comparisons inconclusive.
  • Prioritize systems allowing untrusted local users or using CAN BCM functionality.

Validation and detection

  • Inventory running kernel releases and installed kernel packages across Linux systems.
  • Map each distribution kernel to its vendor advisory or backport status.
  • Confirm the deployed kernel contains the applicable referenced stable fix.
  • After rebooting, verify the active kernel is the remediated build.
Prepared
Confidence
medium
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38003 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38003Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5b48f5711f1c630841ab78dcc061de902f0e37bf, 85cd41070df992d3c0dfd828866fdd243d3b774a, f34f2a18e47b73e48f90a757e1f4aaa8c7d665a1, f1b4e32aca0811aa011c76e5d6cf2fa19224b386, f1b4e32aca0811aa011c76e5d6cf2fa19224b386, f1b4e32aca0811aa011c76e5d6cf2fa19224b386, f1b4e32aca0811aa011c76e5d6cf2fa19224b386, f1b4e32aca0811aa011c76e5d6cf2fa19224b386, fbac09a3b8890003c0c55294c00709f3ae5501bb, edb4baffb9483141a50fb7f7146cfe4a4c0c2db8, 5.4.205, 5.10.130, 5.15.54, 4.19.252, 5.18.11unaffected
LinuxLinux5.19, 0, 5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 6.14.9, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.