Medium 5.5Published Mar 25, 2026

CVE-2026-23362can: bcm: fix locking for bcm_op runtime updates

Updated under an hour ago (Oct 26, 2026, 7:50 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: May 23, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 7595de7bc56e0e52b74e56c90f7e247bf626d628 before 0904037e713f787d1376e1d349c3bdf6c3105881; from fbd8fdc2b218e979cfe422b139b8f74c12419d1f before c85b96eaf766d8f066b1139a17a51efa2f6627ef; from 2a437b86ac5a9893c902f30ef66815bf13587bf6 before 800f26f11ae37b17f58e0001f28a47dd75c26557; 76c84c3728178b2d38d5604e399dfe8b0752645e builds before 70e951afad4c025261fe3c952d2b07237e320a01; from cc55dd28c20a6611e30596019b3b2f636819a4c0 before 8bcf2d847adb82b2c617456f6da17ac5e6c75285; from c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 before 8215ba7bc99e84e66fd6938874ec4330a9d96518; from c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 before f0c349b2c21b220af5ba19f29b885e222958d796; from c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 before c35636e91e392e1540949bbc67932167cb48bc3a; and 9 more ranges	CNA record
linux linux_kernel linux:linux_kernel	from 5.4.294 before 5.5; from 5.10.238 before 5.10.253; from 5.15.185 before 5.15.203; from 6.1.141 before 6.1.167; from 6.6.93 before 6.6.130; from 6.12.31 before 6.12.77; from 6.14.9 before 6.15; from 6.15.1 before 6.18.17; and 9 more ranges	NVD

References

References

https://git.kernel.org/stable/c/0904037e713f787d1376e1d349c3bdf6c3105881	patch
https://git.kernel.org/stable/c/c85b96eaf766d8f066b1139a17a51efa2f6627ef	patch
https://git.kernel.org/stable/c/800f26f11ae37b17f58e0001f28a47dd75c26557	patch
https://git.kernel.org/stable/c/70e951afad4c025261fe3c952d2b07237e320a01	patch
https://git.kernel.org/stable/c/8bcf2d847adb82b2c617456f6da17ac5e6c75285	patch
https://git.kernel.org/stable/c/8215ba7bc99e84e66fd6938874ec4330a9d96518	patch
https://git.kernel.org/stable/c/f0c349b2c21b220af5ba19f29b885e222958d796	patch
https://git.kernel.org/stable/c/c35636e91e392e1540949bbc67932167cb48bc3a	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.