CVE-2026-72120

can: bcm: add missing rcu list annotations and operations

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:52 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot remarked the missing use of list_add_rcu() in bcm_[rx|tx]_setup() to have a proper initialized bcm_op structure when bcm_proc_show() traverses the bcm_op's under rcu_read_lock(). To cover all initial settings of the bcm_op's the list_add_rcu() calls are moved to the end of the setup code. While at it, also fix the mirroring removal side: bcm_release() called bcm_remove_op() - which frees the op via call_rcu() - on ops that were still linked in bo->tx_ops/bo->rx_ops, without list_del_rcu() first. Unlink each op with list_del_rcu() before handing it to bcm_remove_op(), matching the existing pattern in bcm_delete_tx_op()/bcm_delete_rx_op().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0622846db728a5332b917c797c733e202c4620ae19f553a1ddf260da6570ed8f8d91a8c87f49b63a1f912f8484e9c4396378c39460bbea0af681f3195.10.2385.15.1855.4.2946.1.1416.12.316.14.96.156.6.93622846db728a5332b917c797c733e202c4620ae63567ecd99a24495208dc860d50fb17440043006659701c0b954ccdb4a916a4ad59bbc16e726d42c6d7d458c41b98a5c1670cbd36f2923c37de51cf57c9db92d5f0eadca30884af75c53d601edc512eedac5e6249159ac255dad9781793dbe5908ac9ddb
Vendor states this is fixed in 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d (fixed)
Vendor states this is fixed in 4e22e8b505f877573bbdfdbcb680babad9b2f7a1 (fixed)
Vendor states this is fixed in 7b2c3eabc4dafc062a25e10711154f2107526a78 (fixed)
Vendor states this is fixed in 8357255e56dc1aaa437e3c53ee9385de984e0d57 (fixed)
Vendor states this is fixed in 8e1c7257c81577130f5ce90f69b2a2c3ce63f957 (fixed)
Vendor states this is fixed in b06a4a397ac826603f39875cb7c7819a41365196 (fixed)
Vendor states this is fixed in eb1c26eab4d1f0b4450439b4b88c3e73faf1da98 (fixed)
Vendor states this is fixed in f53bdab85e64eb57d6899a30d1307fd5a3639cc7 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card