CVE-2026-72126

CVE CVE-2026-72126EUVD EUVD-2026-58884Published 2026-08-15T05:53:03.000ZLast changed 2026-08-17T05:40:40.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.6.145; patch: 6.12.97; patch: 0; 5.10.50 <5.10.261; 14a4696bc3118ba49da28f79280e1d55603aa737 <cb6abc584a1bfab107ac003d64948a4aef1730aa; 14a4696bc3118ba49da28f79280e1d55603aa737 <b88a511308779c225005d7994b8744561bdbafbc; 14a4696bc3118ba49da28f79280e1d55603aa737 <6280eda96e0707264849fa7d036fed873c1f8a6d; patch: 6.18.40; 22bfa94db2ef6900c790884fa9461486516626e9 <945d9894502cd9124f5d676181c542ed2000f7c0; 14a4696bc3118ba49da28f79280e1d55603aa737 <b8278ff605187ef3fa0f2705e93251cce4c4f8ee; patch: 5.10.261; 14a4696bc3118ba49da28f79280e1d55603aa737 <9b1a02e0d980ac6b0e36a90378f847062f81d7e4; patch: 6.1.178; patch: 5.15.212; ebf91625b3e404bd2b4b694c7ee71c1e8f8bd08f; 14a4696bc3118ba49da28f79280e1d55603aa737 <59672aa4bcd8d32172c1ff6a179583981d6acabc; 14a4696bc3118ba49da28f79280e1d55603aa737 <15413a082df69175c2f96aeab4c26fe1ff7cff03; 80c6ddf771df2ef786f28c1ca5919b3f1080091b; patch: 7.2; patch: 7.1.5; 5.13.2 <5.14; 5.12.17 <5.13; 5.14

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.