ravb: Fix use-after-free issue in ravb_tx_timeout_work()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 105abd68ad8f781985113aee2e92e0702b133705, Kernel 3971442870713de527684398416970cf025b4f89, Kernel 616761cf9df9af838c0a1a1232a69322a9eb67e6 and 3 more.
In the Linux kernel, the following vulnerability has been resolved: ravb: Fix use-after-free issue in ravb_tx_timeout_work() The ravb_stop() should call cancel_work_sync(). Otherwise, ravb_tx_timeout_work() is possible to use the freed priv after ravb_remove() was called like below: CPU0 CPU1 ravb_tx_timeout() ravb_remove() unregister_netdev() free_netdev(ndev) // free priv ravb_tx_timeout_work() // use priv unregister_netdev() will call .ndo_stop() so that ravb_stop() is called. And, after phy_stop() is called, netif_carrier_off() is also called. So that .ndo_tx_timeout() will not be called after phy_stop().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.2, >=c156633f1353264634135dea86ffcae74f2122fc <105abd68ad8f781985113aee2e92e0702b133705, >=c156633f1353264634135dea86ffcae74f2122fc <3971442870713de527684398416970cf025b4f89, >=c156633f1353264634135dea86ffcae74f2122fc <616761cf9df9af838c0a1a1232a69322a9eb67e6, >=c156633f1353264634135dea86ffcae74f2122fc <65d34cfd4e347054eb4193bc95d9da7eaa72dee5, >=c156633f1353264634135dea86ffcae74f2122fc <6f6fa8061f756aedb93af12a8a5d3cf659127965, >=c156633f1353264634135dea86ffcae74f2122fc <db9aafa19547833240f58c2998aed7baf414dc82 | 105abd68ad8f781985113aee2e92e0702b133705, 3971442870713de527684398416970cf025b4f89, 616761cf9df9af838c0a1a1232a69322a9eb67e6, 65d34cfd4e347054eb4193bc95d9da7eaa72dee5, 6f6fa8061f756aedb93af12a8a5d3cf659127965, db9aafa19547833240f58c2998aed7baf414dc82 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket