Vulnerability in Kernel: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
Summary
GSD-2022-1000086: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink(). Affects Kernel versions >= ba7d49b1f0f8e5f24294a880ed576964059af5ef, < 2cf180360d66bd657e606c1217e0e668e6faa303. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Kernel is a crucial component of the Linux operating system, responsible for managing communication between hardware and software. It provides essential functionalities such as device drivers, memory management, and process scheduling. The rtnetlink subsystem within the Kernel handles network-related operations, including configuring network interfaces. This vulnerability specifically affects the __rtnl_newlink() function in rtnetlink, which is responsible for creating new network links. The vulnerability arises from a failure to refresh the master_dev/m_ops, potentially leading to incorrect behavior or security issues.
Vulnerability Detail
The vulnerability in __rtnl_newlink() within the rtnetlink subsystem of the Kernel allows for the possibility of incorrect behavior or security issues. When creating new network links, the function fails to refresh the master_dev/m_ops, which can result in outdated or incorrect information being used. This could potentially lead to network misconfigurations, data leaks, or even privilege escalation attacks. The vulnerability was introduced in version v3.14 of the Kernel and has been fixed in version v4.9.300.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, users can manually refresh the master_dev/m_ops in __rtnl_newlink() by modifying the affected code. Here is an example of the modified code:
// Refresh master_dev/m_ops
if (dev->master_dev) {
dev->master_dev->m_ops = dev->master_dev->type->netdev_ops;
}
Conclusion
In conclusion, the vulnerability in Kernel's rtnetlink subsystem can lead to network misconfigurations, data leaks, or privilege escalation attacks. It is crucial to update the Kernel to version v4.9.300 or later to mitigate this vulnerability. Alternatively, users can apply the provided workaround. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in network misconfigurations, data leaks, or privilege escalation attacks.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze and alert you in real-time.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the recommended fixes to ensure the security and stability of your system.
Yes, this vulnerability can potentially be exploited remotely if an attacker can gain access to the affected network interface. It is crucial to apply the necessary fixes to mitigate the risk.
The recommended fix is to update the Kernel to the latest version. However, if updating is not feasible, the provided workaround can be implemented to manually refresh the master_dev/m_ops in __rtnl_newlink().
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
