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.
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-03-25 11:16
Updated : 2026-06-17 10:21
NVD link : CVE-2026-23362
Mitre link : CVE-2026-23362
CVE.ORG link : CVE-2026-23362
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-667
Improper Locking
