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

> A missing lock initialization in the Linux kernel CAN BCM module can lead to a race condition and potential denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2026
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2026-23362, DEBIAN-CVE-2026-23362, GHSA-57pc-f5j8-25x4, ROOT-OS-DEBIAN-11-CVE-2026-23362, ROOT-OS-DEBIAN-12-CVE-2026-23362, ROOT-OS-DEBIAN-13-CVE-2026-23362, ROOT-OS-UBUNTU-2204-CVE-2026-23362, ROOT-OS-UBUNTU-2404-CVE-2026-23362, UBUNTU-CVE-2026-23362

## What is CVE-2026-23362?

CVE-2026-23362 is a medium-severity vulnerability in Linux kernel, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2026-23362?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-23362?

Apply the vendor's patch.

## Is CVE-2026-23362 being exploited?

There is no known exploitation of CVE-2026-23362 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23362 and fix it if it is affected.

What it is: CVE-2026-23362 is a medium-severity vulnerability in Linux kernel, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23362 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23362/ (Markdown: https://insights.sbomify.com/CVE-2026-23362/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23362
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23362
- OSV: https://osv.dev/vulnerability/CVE-2026-23362

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23362/
Summaries are generated and may contain mistakes; the official description above is the record.