First published: Thu Jun 20 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=3.14<4.9.300 | |
Linux Kernel | >=4.10<4.14.265 | |
Linux Kernel | >=4.15<4.19.228 | |
Linux Kernel | >=4.20<5.4.177 | |
Linux Kernel | >=5.5<5.10.97 | |
Linux Kernel | >=5.11<5.15.20 | |
Linux Kernel | >=5.16<5.16.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-48742 has not been assigned a specific severity score yet.
To mitigate CVE-2022-48742, update the Linux kernel to a version above the affected ranges.
CVE-2022-48742 affects Linux kernel versions between 3.14 and 4.9.300, 4.10 and 4.14.265, 4.15 and 4.19.228, 4.20 and 5.4.177, 5.5 and 5.10.97, 5.11 and 5.15.20, and 5.16 and 5.16.6.
CVE-2022-48742 impacts the rtnetlink component of the Linux kernel.
Yes, CVE-2022-48742 has the potential to trigger a use-after-free condition.