← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-72126

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-72126

Key Details

CVECVE-2026-72126
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

In the Linux kernel, the following vulnerability has been resolved:

can: isotp: use unconditional synchronize_rcu() in isotp_release()

isotp_notify() unregisters the (RCU) CAN filters via can_rx_unregister()

and clears so->bound without waiting for a grace period. isotp_release()

uses so->bound to decide whether it needs to call synchronize_rcu()

before cancelling so->rxtimer, so when NETDEV_UNREGISTER runs first it

skips that synchronize_rcu() and can cancel the timer while an

in-flight isotp_rcv() is still executing and about to re-arm it via

isotp_send_fc(), leading to a use-after-free timer callback on the

freed socket.

sakisho-bot remarked a problem with rtnl_lock held in isotp_notify(),

therefore make isotp_release() always call synchronize_rcu() before

cancelling the timers, regardless of so->bound. This still closes the

original race (isotp_notify() clearing so->bound without waiting for

in-flight isotp_rcv() callers before isotp_release() cancels the RX

timer) without adding any RCU wait to the netdevice notifier path. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-72126
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-72126
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.