Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-23362

can: bcm: fix locking for bcm_op runtime updates

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, and 2 more
None on Exploit-DB, Metasploit or GitHub

Summary

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.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux 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 Linux

    6.15

References 8

git.kernel.org