phylib: fix potential use-after-free
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bafbdd527d569c8200521f2f7579f65a044271be · < cbda1b16687580d5beee38273f6241ae3725960c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
phylib: fix potential use-after-free
Commit bafbdd527d56 ("phylib: Add device reset GPIO support") added call to phy_device_reset(phydev) after the put_device() call in phy_detach().
The comment before the put_device() call says that the phydev might go away with put_device().
Fix potential use-after-free by calling phy_device_reset() before put_device().
From the CVE record · Linux
In the Linux kernel’s phylib, phy_detach() may use a PHY device after put_device() frees it. The input does not establish what an attacker could do or whether triggering this requires network or local access, authentication, or user interaction.
Anyone running the Linux kernel should check whether their version contains this phylib issue; affected versions are not specified.