CVE-2026-23362
In the Linux kernel, the following vulnerability has been resolved: …
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 now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/70e951afad4c025261fe3c952d2b07237e320a01
- git.kernel.org/stable/c/800f26f11ae37b17f58e0001f28a47dd75c26557
- git.kernel.org/stable/c/8215ba7bc99e84e66fd6938874ec4330a9d96518
- git.kernel.org/stable/c/8bcf2d847adb82b2c617456f6da17ac5e6c75285
- git.kernel.org/stable/c/c35636e91e392e1540949bbc67932167cb48bc3a
- git.kernel.org/stable/c/f0c349b2c21b220af5ba19f29b885e222958d796
- git.kernel.org/stable/c/0904037e713f787d1376e1d349c3bdf6c3105881
- git.kernel.org/stable/c/c85b96eaf766d8f066b1139a17a51efa2f6627ef
- nvd.nist.gov/vuln/detail/CVE-2026-23362
- cve.org/CVERecord?id=CVE-2026-23362
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.