CVE-2026-72125: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER
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 0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96, 20bab8b88baac140ca3701116e1d486c7f51e311, 33b9cd9245e2a4b800f99ed1cc53d64960614152.
Low priority for now. Upgrade to Linux Linux 0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96, 20bab8b88baac140ca3701116e1d486c7f51e311, 33b9cd9245e2a4b800f99ed1cc53d64960614152 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: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER isotp_release() looked up the bound network device via dev_get_by_index() using the stored ifindex. During device unregistration the device is unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier chain runs, so a concurrent isotp_release() could find no device, skip can_rx_unregister() entirely, and still proceed to free the socket. Since isotp_release() had already removed itself from the isotp notifier list at that point, isotp_notify() would never get a chance to clean up either, leaving a stale CAN filter that keeps pointing at the freed socket. Fix this the same way raw.c already does: hold a tracked reference to the bound net_device in the socket (so->dev/so->dev_tracker) from bind() onward instead of re-resolving it from the ifindex, and serialize bind()/release() with rtnl_lock() so that so->dev is always consistent with what the NETDEV_UNREGISTER notifier sees. so->dev stays valid regardless of ifindex-hash unlisting, and is only ever cleared by whichever of isotp_release()/isotp_notify() gets there first, so the filter is always removed exactly once. isotp_bind() now rejects a (re)bind with -EAGAIN while so->[tx|rx].state isn't ISOTP_IDLE yet, so a timer left running by a prior NETDEV_UNREGISTER can't act on a newly bound so->ifindex. Both checks share the same lock_sock() section, so there is no window in which a concurrent isotp_notify() clearing so->bound could be missed.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 5th 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
- 5.10affected
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before f311bbb29bb06aaab69ba45a6e4b11323d20b8f9affected · git
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before 8e018f4335590460ebcf0c2b493ed38ba1a35204affected · git
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before 33b9cd9245e2a4b800f99ed1cc53d64960614152affected · git
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before 0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96affected · git
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before 43884dc7963beef2328f507f4fe680bdc173eb80affected · git
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before 7bef39ba76eb7307ed22a50329e0f5776dbeda58affected · git
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before e442b62ba5a7756c17e05a77b32cdd085a2b6138affected · git
- e057dd3fc20ffb3d7f150af46542a51b59b90127 and later · before 20bab8b88baac140ca3701116e1d486c7f51e311affected · git
- before 5.10not affected · 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-72123Aug 15, 2026 · can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF31Monitor
- ← EarlierCVE-2026-72124Aug 15, 2026 · can: isotp: serialize TX state transitions under so->rx_lock35Monitor
- Later →CVE-2026-72126Aug 15, 2026 · can: isotp: use unconditional synchronize_rcu() in isotp_release()31Monitor
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 | 0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96 | Vendor (CNA) |
| Linux Linux | 20bab8b88baac140ca3701116e1d486c7f51e311 | Vendor (CNA) |
| Linux Linux | 33b9cd9245e2a4b800f99ed1cc53d64960614152 | Vendor (CNA) |
| Linux Linux | 43884dc7963beef2328f507f4fe680bdc173eb80 | Vendor (CNA) |
| Linux Linux | 7bef39ba76eb7307ed22a50329e0f5776dbeda58 | Vendor (CNA) |
| Linux Linux | 8e018f4335590460ebcf0c2b493ed38ba1a35204 | Vendor (CNA) |
| Linux Linux | e442b62ba5a7756c17e05a77b32cdd085a2b6138 | Vendor (CNA) |
| Linux Linux | f311bbb29bb06aaab69ba45a6e4b11323d20b8f9 | 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).
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/20bab8b88baac140ca3701116e1d486c7f51e311
- git.kernel.org/stable/c/33b9cd9245e2a4b800f99ed1cc53d64960614152
- git.kernel.org/stable/c/43884dc7963beef2328f507f4fe680bdc173eb80
- git.kernel.org/stable/c/7bef39ba76eb7307ed22a50329e0f5776dbeda58
- git.kernel.org/stable/c/8e018f4335590460ebcf0c2b493ed38ba1a35204
- git.kernel.org/stable/c/e442b62ba5a7756c17e05a77b32cdd085a2b6138
- git.kernel.org/stable/c/f311bbb29bb06aaab69ba45a6e4b11323d20b8f9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.