can: isotp: use unconditional synchronize_rcu() in isotp_release()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.14, Kernel 59672aa4bcd8d32172c1ff6a179583981d6acabc, Kernel 6280eda96e0707264849fa7d036fed873c1f8a6d and 14 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5.13.2 <5.14, >=14a4696bc3118ba49da28f79280e1d55603aa737 <59672aa4bcd8d32172c1ff6a179583981d6acabc, >=14a4696bc3118ba49da28f79280e1d55603aa737 <6280eda96e0707264849fa7d036fed873c1f8a6d, >=14a4696bc3118ba49da28f79280e1d55603aa737 <9b1a02e0d980ac6b0e36a90378f847062f81d7e4, >=14a4696bc3118ba49da28f79280e1d55603aa737 <b8278ff605187ef3fa0f2705e93251cce4c4f8ee, >=14a4696bc3118ba49da28f79280e1d55603aa737 <b88a511308779c225005d7994b8744561bdbafbc, >=14a4696bc3118ba49da28f79280e1d55603aa737 <cb6abc584a1bfab107ac003d64948a4aef1730aa, >=22bfa94db2ef6900c790884fa9461486516626e9 <945d9894502cd9124f5d676181c542ed2000f7c0, >=5.10.50 <5.10.261, >=5.12.17 <5.13, =5.14, =80c6ddf771df2ef786f28c1ca5919b3f1080091b, =ebf91625b3e404bd2b4b694c7ee71c1e8f8bd08f, >=14a4696bc3118ba49da28f79280e1d55603aa737 <15413a082df69175c2f96aeab4c26fe1ff7cff03 | 5.14, 59672aa4bcd8d32172c1ff6a179583981d6acabc, 6280eda96e0707264849fa7d036fed873c1f8a6d, 9b1a02e0d980ac6b0e36a90378f847062f81d7e4, b8278ff605187ef3fa0f2705e93251cce4c4f8ee, b88a511308779c225005d7994b8744561bdbafbc, cb6abc584a1bfab107ac003d64948a4aef1730aa, 945d9894502cd9124f5d676181c542ed2000f7c0, 5.10.261, 5.13, 15413a082df69175c2f96aeab4c26fe1ff7cff03 |
| linux-kernel: Kernel | >=5.12.17 <5.13, >=5.13.2 <5.14, >=5.14.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=5.10.50 <5.10.261 | 5.13, 5.14, 5.15.212, 6.1.178, 6.18.40, 7.1.5, 6.6.145, 6.12.97, 5.10.261 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket