Linux Kernel up to 7.2-rc3 bcm net/can/bcm.c bcm_tx_setup race condition

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.48

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.147/6.12.100/6.18.41/7.1.4/7.2-rc3. It has been classified as very critical. The affected element is the function bcm_tx_setup of the file net/can/bcm.c of the component bcm. The manipulation leads to race condition. This vulnerability is referenced as CVE-2026-72119. The attack can only be performed from a local environment. No exploit is available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.147/6.12.100/6.18.41/7.1.4/7.2-rc3 and classified as very critical. This issue affects the function bcm_tx_setup of the file net/can/bcm.c of the component bcm. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcm_tx_lock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc()'d buffer and validate it there, mirroring the approach already used in bcm_rx_setup(). Only copy the validated data into op->frames while holding op->bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler() can no longer observe a partially updated or unvalidated frame. Add a missing error path for memcpy_from_msg() when copying CAN frame data from userspace. Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup() under op->bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the torn 64-bit ktime_t read on 32-bit platforms.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-72119 since 08/09/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 6.6.148, 6.12.101, 6.18.42, 7.1.5 or 7.2-rc4 eliminates this vulnerability. Applying the patch 52f06e7603780de100233713ddaf971d422e10ef/972fd66bb08fdef1090abe43196ca8da07216d13/bd46f55dec608daa44b45dcf3328517630ad8e40/337f966c00662d81ad82cf5a4bbb150b2e32c0d4/12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider 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: Race condition
CWE: CWE-362
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 6.6.148/6.12.101/6.18.42/7.1.5/7.2-rc4
Patch: 52f06e7603780de100233713ddaf971d422e10ef/972fd66bb08fdef1090abe43196ca8da07216d13/bd46f55dec608daa44b45dcf3328517630ad8e40/337f966c00662d81ad82cf5a4bbb150b2e32c0d4/12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc

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-72119 (🔒)
GCVE (CVE): GCVE-0-2026-72119
GCVE (VulDB): GCVE-100-390605

Entryinfo

Created: 08/15/2026 13:15
Changes: 08/15/2026 13:15 (60)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!