CVE-2026-72119: can: bcm: extend bcm_tx_lock usage for data and timer updates
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc, 337f966c00662d81ad82cf5a4bbb150b2e32c0d4, 37917e432e50b7de2b64230974380132a30f7270.
Low priority for now. Upgrade to Linux Linux 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc, 337f966c00662d81ad82cf5a4bbb150b2e32c0d4, 37917e432e50b7de2b64230974380132a30f7270 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 8f1c022541bf5a923c8d6fa483112c15250f30a4, c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, 6.15affected
- 7595de7bc56e0e52b74e56c90f7e247bf626d628 and later · before a538b072ee074c9b41b9d9c15a6861a963e30755affected · git
- fbd8fdc2b218e979cfe422b139b8f74c12419d1f and later · before 63422347b4c782f429748b2a09cd3cf3b77e6abdaffected · git
- 2a437b86ac5a9893c902f30ef66815bf13587bf6 and later · before 37917e432e50b7de2b64230974380132a30f7270affected · git
- 76c84c3728178b2d38d5604e399dfe8b0752645e and later · before 52f06e7603780de100233713ddaf971d422e10efaffected · git
- cc55dd28c20a6611e30596019b3b2f636819a4c0 and later · before 972fd66bb08fdef1090abe43196ca8da07216d13affected · git
- c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and later · before bd46f55dec608daa44b45dcf3328517630ad8e40affected · git
- c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and later · before 337f966c00662d81ad82cf5a4bbb150b2e32c0d4affected · git
- c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and later · before 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebcaffected · git
- 5.10.238 and later · before 5.10.265affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72117Aug 15, 2026 · can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler()0Monitor
- ← EarlierCVE-2026-72118Aug 15, 2026 · can: bcm: fix CAN frame rx/tx statistics0Monitor
- Later →CVE-2026-72120Aug 15, 2026 · can: bcm: add missing rcu list annotations and operations31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc | Vendor (CNA) |
| Linux Linux | 337f966c00662d81ad82cf5a4bbb150b2e32c0d4 | Vendor (CNA) |
| Linux Linux | 37917e432e50b7de2b64230974380132a30f7270 | Vendor (CNA) |
| Linux Linux | 5.10.265 | Vendor (CNA) |
| Linux Linux | 5.15.216 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 52f06e7603780de100233713ddaf971d422e10ef | Vendor (CNA) |
| Linux Linux | 6.1.183 | Vendor (CNA) |
| Linux Linux | 6.12.101 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 6.6.148 | Vendor (CNA) |
| Linux Linux | 63422347b4c782f429748b2a09cd3cf3b77e6abd | Vendor (CNA) |
| Linux Linux | 972fd66bb08fdef1090abe43196ca8da07216d13 | Vendor (CNA) |
| Linux Linux | a538b072ee074c9b41b9d9c15a6861a963e30755 | Vendor (CNA) |
| Linux Linux | bd46f55dec608daa44b45dcf3328517630ad8e40 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/337f966c00662d81ad82cf5a4bbb150b2e32c0d4
- git.kernel.org/stable/c/37917e432e50b7de2b64230974380132a30f7270
- git.kernel.org/stable/c/52f06e7603780de100233713ddaf971d422e10ef
- git.kernel.org/stable/c/63422347b4c782f429748b2a09cd3cf3b77e6abd
- git.kernel.org/stable/c/972fd66bb08fdef1090abe43196ca8da07216d13
- git.kernel.org/stable/c/a538b072ee074c9b41b9d9c15a6861a963e30755
- git.kernel.org/stable/c/bd46f55dec608daa44b45dcf3328517630ad8e40
Vendor advisories and official records. Exploit/PoC links are deliberately left out.