CVE-2026-72119

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

can: bcm: extend bcm_tx_lock usage for data and timer updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bd46f55dec608daa44b45dcf3328517630ad8e40
generic

can: bcm: extend bcm_tx_lock usage for data and timer updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/972fd66bb08fdef1090abe43196ca8da07216d13
generic

can: bcm: extend bcm_tx_lock usage for data and timer updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52f06e7603780de100233713ddaf971d422e10ef
generic

can: bcm: extend bcm_tx_lock usage for data and timer updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/337f966c00662d81ad82cf5a4bbb150b2e32c0d4
generic

can: bcm: extend bcm_tx_lock usage for data and timer updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc

Vendor Advisories for CVE-2026-72119(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 19:23 UTCGHSA enrichment
  3. 2026-08-20 06:31 UTCGHSA enrichment
  4. 2026-08-19 17:39 UTCEG score recompute
  5. 2026-08-19 17:39 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:46 UTCEG score recompute
  8. 2026-08-19 16:46 UTCGHSA enrichment
  9. 2026-08-19 09:50 UTCGHSA enrichment
  10. 2026-08-18 20:59 UTCEG score recompute
  11. 2026-08-18 20:59 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 08:06 UTCGHSA enrichment
  15. 2026-08-17 19:12 UTCEG score recompute
  16. 2026-08-17 19:12 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:19 UTCEG score recompute
  19. 2026-08-17 06:18 UTCGHSA enrichment
  20. 2026-08-17 06:00 UTCEG score recompute▲ 7.80
  21. 2026-08-17 06:00 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  23. 2026-08-17 05:33 UTCEG score recompute
  24. 2026-08-17 05:33 UTCGHSA enrichment
  25. 2026-08-17 05:24 UTCMITRE cvelistV5
Show 7 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:43 UTCGHSA enrichment
  5. 2026-08-15 06:23 UTCNVD update
  6. 2026-08-15 06:12 UTCEG score recompute
  7. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72119?
CVE-2026-72119 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcmtxlock 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 bcmrxsetup(). Only copy the…
When was CVE-2026-72119 disclosed?
CVE-2026-72119 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72119 actively exploited?
CVE-2026-72119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72119?
CVE-2026-72119 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72119, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72119

Explore →

Is Your Infrastructure Affected by CVE-2026-72119?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs