LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23362: can: bcm: fix locking for bcm_op runtime updates

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix locking for bcm_op runtime updates Commit c2aba69d0c36 ("can: bcm: add locking for bcm_op runtime updates") added a locking for some variables that can be modified at runtime when updating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup(). Usually the RX_SETUP only handles and filters incoming traffic with one exception: When the RX_RTR_FRAME flag is set a predefined CAN frame is sent when a specific RTR frame is received. Therefore the rx bcm_op uses bcm_can_tx() which uses the bcm_tx_lock that was only initialized in bcm_tx_setup(). Add the missing spin_lock_init() when allocating the bcm_op in bcm_rx_setup() to handle the RTR case properly.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23362 is a Linux kernel CAN Broadcast Manager locking bug. It affects a narrow area used for CAN bus messaging, common in embedded, automotive, and industrial systems. The provided sources do not state business impact, CVSS severity, or active exploitation, so urgency depends mainly on whether affected systems expose or use Linux CAN BCM functionality.

Executive priority

Handle through normal kernel vulnerability management unless CAN-enabled systems are business critical. Raise priority for automotive, industrial, or embedded environments where CAN bus reliability matters and kernel updates require planned maintenance windows.

Technical view

The bug is in Linux kernel CAN BCM. RX setup can transmit a predefined CAN frame when RX_RTR_FRAME is set, but the transmit lock used by bcm_can_tx() was only initialized in TX setup. The fix initializes bcm_tx_lock when allocating the RX bcm_op, covering the RTR transmit path.

Likely exposure

Most likely exposed assets are Linux systems using SocketCAN CAN BCM, especially embedded, vehicle, lab, and industrial hosts. General-purpose servers without CAN interfaces or CAN BCM usage are less likely exposed. Version mapping is commit and kernel-series based, so distribution package status must be verified separately.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, exploit availability, CVSS, or CWE data. It also does not define attacker prerequisites or impact. Treat exploitability as unconfirmed until Linux vendor advisories or distribution security notes provide more detail.

Researcher notes

The source describes a missing spin_lock_init() in bcm_rx_setup() for RX_RTR_FRAME behavior. The public bundle does not provide a crash signature, privilege boundary, CVSS vector, or reproduction details. Avoid overstating impact until upstream or distribution advisories clarify consequences.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Prioritize embedded and industrial Linux systems using CAN interfaces.
  • Check distribution advisories before assuming upstream version numbers map directly.
  • Disable or restrict CAN BCM use where operationally unnecessary.
  • Monitor Linux stable and vendor security notes for impact clarification.

Validation and detection

  • Inventory Linux hosts with CAN interfaces or SocketCAN usage.
  • Map running kernels to vendor advisories and fixed stable commits.
  • Confirm whether CAN BCM is enabled or used by applications.
  • Review kernel package changelogs for the bcm_tx_lock RX setup fix.
  • Document systems where vendor fix availability remains unknown.
Prepared
Confidence
medium
Sources
10

Public sources used

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-2026-23362 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7595de7bc56e0e52b74e56c90f7e247bf626d628, fbd8fdc2b218e979cfe422b139b8f74c12419d1f, 2a437b86ac5a9893c902f30ef66815bf13587bf6, 76c84c3728178b2d38d5604e399dfe8b0752645e, cc55dd28c20a6611e30596019b3b2f636819a4c0, c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, 8f1c022541bf5a923c8d6fa483112c15250f30a4, c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 5.4.294, 6.14.9unaffected
LinuxLinux6.15, 0, 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

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