CVE-2026-23362
Published: March 26, 2026Last modified: April 9, 2026
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.
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 5.5 |
| Attack Vector | LOCAL |
| Attack complexity | LOW |
| Privileges required | LOW |
| User interaction | NONE |
| Scope | UNCHANGED |
| Confidentiality | NONE |
| Integrity impact | NONE |
| Availability impact | HIGH |
| Vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Status
| Product | Release | Package | Status |
|---|---|---|---|
| Alpaquita Linux | 23 LTS | linux-lts | Fixed (6.1.167-r0) |
| 25 LTS | linux-lts | Fixed (6.12.80-r0) | |
| Stream | linux-lts | Fixed (6.12.80-r0) |
References
- https://git.kernel.org/stable/c/0904037e713f787d1376e1d349c3bdf6c3105881
- https://git.kernel.org/stable/c/70e951afad4c025261fe3c952d2b07237e320a01
- https://git.kernel.org/stable/c/800f26f11ae37b17f58e0001f28a47dd75c26557
- https://git.kernel.org/stable/c/8215ba7bc99e84e66fd6938874ec4330a9d96518
- https://git.kernel.org/stable/c/8bcf2d847adb82b2c617456f6da17ac5e6c75285
- https://git.kernel.org/stable/c/c35636e91e392e1540949bbc67932167cb48bc3a
- https://git.kernel.org/stable/c/c85b96eaf766d8f066b1139a17a51efa2f6627ef
- https://git.kernel.org/stable/c/f0c349b2c21b220af5ba19f29b885e222958d796