CVE-2026-72120: can: bcm: add missing rcu list annotations and operations
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 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d, 4e22e8b505f877573bbdfdbcb680babad9b2f7a1, 5.10.261.
Low priority for now. Upgrade to Linux Linux 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d, 4e22e8b505f877573bbdfdbcb680babad9b2f7a1, 5.10.261 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: 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().
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Monitor
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 19f553a1ddf260da6570ed8f8d91a8c87f49b63a, 7c9db92d5f0eadca30884af75c53d601edc512ee, 6.15affected
- 659701c0b954ccdb4a916a4ad59bbc16e726d42c and later · before 8357255e56dc1aaa437e3c53ee9385de984e0d57affected · git
- 0622846db728a5332b917c797c733e202c4620ae and later · before 8e1c7257c81577130f5ce90f69b2a2c3ce63f957affected · git
- 6d7d458c41b98a5c1670cbd36f2923c37de51cf5 and later · before eb1c26eab4d1f0b4450439b4b88c3e73faf1da98affected · git
- 1f912f8484e9c4396378c39460bbea0af681f319 and later · before f53bdab85e64eb57d6899a30d1307fd5a3639cc7affected · git
- 63567ecd99a24495208dc860d50fb17440043006 and later · before 4e22e8b505f877573bbdfdbcb680babad9b2f7a1affected · git
- dac5e6249159ac255dad9781793dbe5908ac9ddb and later · before b06a4a397ac826603f39875cb7c7819a41365196affected · git
- dac5e6249159ac255dad9781793dbe5908ac9ddb and later · before 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1daffected · git
- dac5e6249159ac255dad9781793dbe5908ac9ddb and later · before 7b2c3eabc4dafc062a25e10711154f2107526a78affected · git
- 5.10.238 and later · before 5.10.261affected · 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-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-72118Aug 15, 2026 · can: bcm: fix CAN frame rx/tx statistics0Monitor
- ← EarlierCVE-2026-72119Aug 15, 2026 · can: bcm: extend bcm_tx_lock usage for data and timer updates31Monitor
- Later →CVE-2026-72121Aug 15, 2026 · can: bcm: add locking when updating filter and timer values35Monitor
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 | 30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d | Vendor (CNA) |
| Linux Linux | 4e22e8b505f877573bbdfdbcb680babad9b2f7a1 | Vendor (CNA) |
| Linux Linux | 5.10.261 | Vendor (CNA) |
| Linux Linux | 5.15.212 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.12.97 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 7b2c3eabc4dafc062a25e10711154f2107526a78 | Vendor (CNA) |
| Linux Linux | 8357255e56dc1aaa437e3c53ee9385de984e0d57 | Vendor (CNA) |
| Linux Linux | 8e1c7257c81577130f5ce90f69b2a2c3ce63f957 | Vendor (CNA) |
| Linux Linux | b06a4a397ac826603f39875cb7c7819a41365196 | Vendor (CNA) |
| Linux Linux | eb1c26eab4d1f0b4450439b4b88c3e73faf1da98 | Vendor (CNA) |
| Linux Linux | f53bdab85e64eb57d6899a30d1307fd5a3639cc7 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- 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/4e22e8b505f877573bbdfdbcb680babad9b2f7a1
- git.kernel.org/stable/c/7b2c3eabc4dafc062a25e10711154f2107526a78
- git.kernel.org/stable/c/8357255e56dc1aaa437e3c53ee9385de984e0d57
- git.kernel.org/stable/c/8e1c7257c81577130f5ce90f69b2a2c3ce63f957
- git.kernel.org/stable/c/b06a4a397ac826603f39875cb7c7819a41365196
- git.kernel.org/stable/c/eb1c26eab4d1f0b4450439b4b88c3e73faf1da98
- git.kernel.org/stable/c/f53bdab85e64eb57d6899a30d1307fd5a3639cc7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.