Strix
57.1K

CVE-2026-72120

HIGHCVSS 7.8/10EPSS 0.21%

Last modified

CVE-2026-72120 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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().. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.21%

11.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 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
LinuxLinux6.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-72120?
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().
How severe is CVE-2026-72120?
CVE-2026-72120 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72120?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-72120?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST