What is CVE-2026-72126?

CVE-2026-72126 is a unscored severity Linux kernel vulnerability, affecting Linux kernel versions from 5.10.50 onward and patched in 5.10.261, 5.15.212, 6.1.178 and others. CVE-2026-72126 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-72126?

CVE-2026-72126 has a CVSS score of pending NVD analysis out of 10, rated awaiting scoring severity.

Is there a patch available for CVE-2026-72126?

Yes, CVE-2026-72126 has been patched. Fixed versions include 5.10.261, 5.15.212, 6.1.178 and others. If you are running Linux kernel 5.10.50 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-72126 actively exploited?

CVE-2026-72126 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-72126

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.

Package Linux Kernel

Published 2026-08-15

Last modified 2026-08-15

Patch available

Yes

Affected versions

Linux kernel versions 5.10.50, 5.12.17, 5.13.2, 5.14 and later are affected. Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2-rc4 and their respective stable series.

Affected from

≥ 5.10.50 ≥ 5.12.17 ≥ 5.13.2 ≥ 5.14

Fixed in

✓ 5.10.261 5.10.x ✓ 5.15.212 5.15.x ✓ 6.1.178 6.1.x ✓ 6.6.145 6.6.x ✓ 6.12.97 6.12.x ✓ 6.18.40 6.18.x ✓ 7.1.5 7.1.x ✓ 7.2-rc4

References

8 total

Showing 5 of 8 references View all on NVD

Frequently asked questions

What is CVE-2026-72126?

CVE-2026-72126 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.10.50 onward and has been patched in 5.10.261, 5.15.212, 6.1.178 and others. CVE-2026-72126 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
Is there a patch available for CVE-2026-72126?

Yes. CVE-2026-72126 has been patched. Fixed versions include 5.10.261, 5.15.212, 6.1.178 and others. If you are running Linux kernel 5.10.50 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-72126 actively exploited?

No. CVE-2026-72126 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.