CVE-2026-72119 — can: bcm: extend bcm_tx_lock usage for data and timer updates
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version c4e8a172501e677ebd8ea9d9161d97dc4df56fbdversion 6.15≥ 6.14.9 and < 6.15≥ 5.4.294 and < 5.5≥ 6.12.31 and < 6.12.101≥ 6.6.93 and < 6.6.148≥ 6.1.141 and < 6.1.183≥ 5.15.185 and < 5.15.216 and 10 more≥ 5.10.238 and < 5.10.265≥ 7595de7bc56e0e52b74e56c90f7e247bf626d628 and < a538b072ee074c9b41b9d9c15a6861a963e30755version 8f1c022541bf5a923c8d6fa483112c15250f30a4≥ c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and < 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc≥ c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and < 337f966c00662d81ad82cf5a4bbb150b2e32c0d4≥ c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and < bd46f55dec608daa44b45dcf3328517630ad8e40≥ cc55dd28c20a6611e30596019b3b2f636819a4c0 and < 972fd66bb08fdef1090abe43196ca8da07216d13≥ 76c84c3728178b2d38d5604e399dfe8b0752645e and < 52f06e7603780de100233713ddaf971d422e10ef≥ 2a437b86ac5a9893c902f30ef66815bf13587bf6 and < 37917e432e50b7de2b64230974380132a30f7270≥ fbd8fdc2b218e979cfe422b139b8f74c12419d1f and < 63422347b4c782f429748b2a09cd3cf3b77e6abd |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/37917e432e50b7de2b64230974380132a30f7270
- git.kernel.org/stable/c/a538b072ee074c9b41b9d9c15a6861a963e30755
- git.kernel.org/stable/c/12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc
- git.kernel.org/stable/c/972fd66bb08fdef1090abe43196ca8da07216d13
- git.kernel.org/stable/c/337f966c00662d81ad82cf5a4bbb150b2e32c0d4
- git.kernel.org/stable/c/52f06e7603780de100233713ddaf971d422e10ef
- git.kernel.org/stable/c/63422347b4c782f429748b2a09cd3cf3b77e6abd
- git.kernel.org/stable/c/bd46f55dec608daa44b45dcf3328517630ad8e40
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 17h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 17h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72119 is "can: bcm: extend bcm_tx_lock usage for data and timer updates", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.