Linux Kernel up to 7.2-rc3 bcm bcm_rx_setup/bcm_tx_setup/bcm_release locking

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4$0-$5k0.47+

Summaryinfo

A vulnerability categorized as very critical has been discovered in Linux Kernel up to 7.2-rc3. Impacted is the function bcm_rx_setup/bcm_tx_setup/bcm_release of the component bcm. Executing a manipulation can lead to locking. This vulnerability appears as CVE-2026-72120. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability classified as very critical was found in Linux Kernel up to 7.2-rc3. This vulnerability affects the function bcm_rx_setup/bcm_tx_setup/bcm_release of the component bcm. The manipulation with an unknown input leads to a locking vulnerability. The CWE definition for the vulnerability is CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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

The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-72120 since 08/09/2026. The exploitation appears to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc4 eliminates this vulnerability. Applying the patch 8357255e56dc1aaa437e3c53ee9385de984e0d57/8e1c7257c81577130f5ce90f69b2a2c3ce63f957/eb1c26eab4d1f0b4450439b4b88c3e73faf1da98/f53bdab85e64eb57d6899a30d1307fd5a3639cc7/4e22e8b505f877573bbdfdbcb680babad9b2f7a1/b06a4a397ac826603f39875cb7c7819a41365196/30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d/7b2c3eabc4dafc062a25e10711154f2107526a78 is able to eliminate this problem.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Locking
CWE: CWE-667
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc4
Patch: 8357255e56dc1aaa437e3c53ee9385de984e0d57/8e1c7257c81577130f5ce90f69b2a2c3ce63f957/eb1c26eab4d1f0b4450439b4b88c3e73faf1da98/f53bdab85e64eb57d6899a30d1307fd5a3639cc7/4e22e8b505f877573bbdfdbcb680babad9b2f7a1/b06a4a397ac826603f39875cb7c7819a41365196/30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d/7b2c3eabc4dafc062a25e10711154f2107526a78

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72120 (🔒)
GCVE (CVE): GCVE-0-2026-72120
GCVE (VulDB): GCVE-100-390538

Entryinfo

Created: 08/15/2026 12:32
Changes: 08/15/2026 12:32 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!