ravb: Fix use-after-free issue in ravb_tx_timeout_work()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c156633f1353264634135dea86ffcae74f2122fc · < 3971442870713de527684398416970cf025b4f89| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel's ravb driver can use freed memory if transmit-timeout work runs after the network device is removed. The input does not specify what an attacker can achieve or whether exploitation requires local access, authentication, or user interaction.
Operators running Linux kernels with the ravb driver should check their exposure; affected versions are not specified.