rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ba7d49b1f0f8e5f24294a880ed576964059af5ef · < def5e7070079b2a214b3b1a2fbec623e6fbfe34a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
While looking at one unrelated syzbot bug, I found the replay logic in __rtnl_newlink() to potentially trigger use-after-free.
It is better to clear master_dev and m_ops inside the loop, in case we have to replay it.
From the CVE record · Linux
The Linux kernel's __rtnl_newlink() replay logic can potentially trigger a use-after-free if master_dev and m_ops are not refreshed when the operation is replayed. The input does not specify how an attacker could trigger this, whether authentication or user interaction is required, or the resulting impact.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.