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.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://git.kernel.org/stable/c/2cf180360d66bd657e606c1217e0e668e6faa303 | patch mailing list |
https://git.kernel.org/stable/c/7d9211678c0f0624f74cdff36117ab8316697bb8 | patch mailing list |
https://git.kernel.org/stable/c/a01e60a1ec6bef9be471fb7182a33c6d6f124e93 | patch mailing list |
https://git.kernel.org/stable/c/bd43771ee9759dd9dfae946bff190e2c5a120de5 | patch mailing list |
https://git.kernel.org/stable/c/3bbe2019dd12b8d13671ee6cda055d49637b4c39 | patch mailing list |
https://git.kernel.org/stable/c/def5e7070079b2a214b3b1a2fbec623e6fbfe34a | patch mailing list |
https://git.kernel.org/stable/c/36a9a0aee881940476b254e0352581401b23f210 | patch mailing list |
https://git.kernel.org/stable/c/c6f6f2444bdbe0079e41914a35081530d0409963 | patch mailing list |