Answer in brief
CVE-2026-72120 records a Unknown severity vulnerability in can: bcm: add missing rcu list annotations and operations. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72120 records a Unknown severity vulnerability in can: bcm: add missing rcu list annotations and operations. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=659701c0b954ccdb4a916a4ad59bbc16e726d42c <8357255e56dc1aaa437e3c53ee9385de984e0d57 || >=0622846db728a5332b917c797c733e202c4620ae <8e1c7257c81577130f5ce90f69b2a2c3ce63f957 || >=6d7d458c41b98a5c1670cbd36f2923c37de51cf5 <eb1c26eab4d1f0b4450439b4b88c3e73faf1da98 || >=1f912f8484e9c4396378c39460bbea0af681f319 <f53bdab85e64eb57d6899a30d1307fd5a3639cc7 || >=63567ecd99a24495208dc860d50fb17440043006 <4e22e8b505f877573bbdfdbcb680babad9b2f7a1 || >=dac5e6249159ac255dad9781793dbe5908ac9ddb <b06a4a397ac826603f39875cb7c7819a41365196 || >=dac5e6249159ac255dad9781793dbe5908ac9ddb <30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d || >=dac5e6249159ac255dad9781793dbe5908ac9ddb <7b2c3eabc4dafc062a25e10711154f2107526a78 || 19f553a1ddf260da6570ed8f8d91a8c87f49b63a || 7c9db92d5f0eadca30884af75c53d601edc512ee || >=5.10.238 <5.10.261 || >=5.15.185 <5.15.212 || >=6.1.141 <6.1.178 || >=6.6.93 <6.6.145 || >=6.12.31 <6.12.97 || >=5.4.294 <5.5 || >=6.14.9 <6.15 | 8357255e56dc1aaa437e3c53ee9385de984e0d57, 8e1c7257c81577130f5ce90f69b2a2c3ce63f957, eb1c26eab4d1f0b4450439b4b88c3e73faf1da98, f53bdab85e64eb57d6899a30d1307fd5a3639cc7, 4e22e8b505f877573bbdfdbcb680babad9b2f7a1, b06a4a397ac826603f39875cb7c7819a41365196, 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d, 7b2c3eabc4dafc062a25e10711154f2107526a78, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 5.5, 6.15 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=659701c0b954ccdb4a916a4ad59bbc16e726d42c <8357255e56dc1aaa437e3c53ee9385de984e0d57 || >=0622846db728a5332b917c797c733e202c4620ae <8e1c7257c81577130f5ce90f69b2a2c3ce63f957 || >=6d7d458c41b98a5c1670cbd36f2923c37de51cf5 <eb1c26eab4d1f0b4450439b4b88c3e73faf1da98 || >=1f912f8484e9c4396378c39460bbea0af681f319 <f53bdab85e64eb57d6899a30d1307fd5a3639cc7 || >=63567ecd99a24495208dc860d50fb17440043006 <4e22e8b505f877573bbdfdbcb680babad9b2f7a1 || >=dac5e6249159ac255dad9781793dbe5908ac9ddb <b06a4a397ac826603f39875cb7c7819a41365196 || >=dac5e6249159ac255dad9781793dbe5908ac9ddb <30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d || >=dac5e6249159ac255dad9781793dbe5908ac9ddb <7b2c3eabc4dafc062a25e10711154f2107526a78 || 19f553a1ddf260da6570ed8f8d91a8c87f49b63a || 7c9db92d5f0eadca30884af75c53d601edc512ee || >=5.10.238 <5.10.261 || >=5.15.185 <5.15.212 || >=6.1.141 <6.1.178 || >=6.6.93 <6.6.145 || >=6.12.31 <6.12.97 || >=5.4.294 <5.5 || >=6.14.9 <6.15 | 8357255e56dc1aaa437e3c53ee9385de984e0d57, 8e1c7257c81577130f5ce90f69b2a2c3ce63f957, eb1c26eab4d1f0b4450439b4b88c3e73faf1da98, f53bdab85e64eb57d6899a30d1307fd5a3639cc7, 4e22e8b505f877573bbdfdbcb680babad9b2f7a1, b06a4a397ac826603f39875cb7c7819a41365196, 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d, 7b2c3eabc4dafc062a25e10711154f2107526a78, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 5.5, 6.15 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.