CVE-2026-23362 Details
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.
A vulnerability in the Linux kernel's CAN BCM (Broadcast Communication Management) implementation has been addressed. The issue arose because the RX_SETUP process, which typically manages incoming traffic, did not properly handle cases where the RX_RTR_FRAME flag was set. This flag triggers the transmission of a predefined CAN frame in response to a specific RTR frame. The RX operation relied on a locking mechanism that was only initialized in the TX_SETUP command, leading to potential race conditions. The vulnerability has been fixed by adding the missing initialization for the transmission lock in the RX_SETUP process, ensuring proper handling of RTR frame scenarios.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0904037e713f787d1376e1d349c3bdf6c3105881 | kernel.org | Patch |
| https://git.kernel.org/stable/c/70e951afad4c025261fe3c952d2b07237e320a01 | kernel.org | Patch |
| https://git.kernel.org/stable/c/800f26f11ae37b17f58e0001f28a47dd75c26557 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8215ba7bc99e84e66fd6938874ec4330a9d96518 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8bcf2d847adb82b2c617456f6da17ac5e6c75285 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c35636e91e392e1540949bbc67932167cb48bc3a | kernel.org | Patch |
| https://git.kernel.org/stable/c/c85b96eaf766d8f066b1139a17a51efa2f6627ef | kernel.org | Patch |
| https://git.kernel.org/stable/c/f0c349b2c21b220af5ba19f29b885e222958d796 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.4.294, < 5.5 >= 5.10.238, < 5.10.253 >= 5.15.185, < 5.15.203 >= 6.1.141, < 6.1.167 >= 6.6.93, < 6.6.130 >= 6.12.31, < 6.12.77 >= 6.14.9, < 6.15 >= 6.15.1, < 6.18.17 >= 6.19, < 6.19.7 6.15 - 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 24, 2026 | Initial Analysis | [email protected] |
| Apr 18, 2026 | CVE Modified | kernel.org |
| Mar 25, 2026 | New CVE Received | kernel.org |