CVE-2026-72125 json
can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER
published 2026-08-15 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-58883
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, 6.18.40, 7.1.5, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.101-1
- linux Debian 14 7.1.5-1
- linux-6.12 Debian 12 6.12.101-1~deb12u1
debian advisories DEBIAN-CVE-2026-72125
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-72125
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.84.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.84.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.84.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1
- kernel-obs-build SLE Module for Development Tools 15 SP7 6.4.0-150700.53.84.1
- kernel-default-base SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1.150700.17.47.1
suse advisories SUSE-SU-2026:4706-1SUSE-SU-2026:4640-1
- git.kernel.org/stable/c/f311bbb29bb06aaab69ba45a6e4b11323d20b8f9 commit
- git.kernel.org/stable/c/8e018f4335590460ebcf0c2b493ed38ba1a35204 commit
- git.kernel.org/stable/c/33b9cd9245e2a4b800f99ed1cc53d64960614152 commit
- git.kernel.org/stable/c/0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96 commit
- git.kernel.org/stable/c/43884dc7963beef2328f507f4fe680bdc173eb80 commit
- git.kernel.org/stable/c/7bef39ba76eb7307ed22a50329e0f5776dbeda58 commit
- git.kernel.org/stable/c/e442b62ba5a7756c17e05a77b32cdd085a2b6138 commit
- git.kernel.org/stable/c/20bab8b88baac140ca3701116e1d486c7f51e311 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-72125 updated cvss 7.0
kernel: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/f311bbb29bb06aaab69ba45a6e4b11323d20b8f9
- git.kernel.org /stable/c/8e018f4335590460ebcf0c2b493ed38ba1a35204
- git.kernel.org /stable/c/33b9cd9245e2a4b800f99ed1cc53d64960614152
- git.kernel.org /stable/c/0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96
- git.kernel.org /stable/c/43884dc7963beef2328f507f4fe680bdc173eb80
- git.kernel.org /stable/c/7bef39ba76eb7307ed22a50329e0f5776dbeda58
- git.kernel.org /stable/c/e442b62ba5a7756c17e05a77b32cdd085a2b6138
- git.kernel.org /stable/c/20bab8b88baac140ca3701116e1d486c7f51e311
Sources
- CVE List CVE-2026-72125
- NVD CVE-2026-72125
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.