Acquire RTNL before calling ip[6]mr_free_table() on failure path in Kernel
Summary
GSD-2022-1000338: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path. Affects Kernel versions >= f243e5a7859a24d10975afb9a1708cac624ba6f1, < 16dcfde98a25340ff0f7879a16bea141d824a196. 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 that acts as the bridge between the hardware and software layers. It provides essential services and functions, such as managing system resources, handling device drivers, and facilitating communication between different software components. The Kernel is responsible for maintaining the stability, security, and performance of the entire system. However, a vulnerability has been discovered in the Kernel related to the ipmr and ip6mr modules.
Vulnerability Detail
The ipmr and ip6mr modules in the Kernel are susceptible to a vulnerability that can be exploited on the failure path. Specifically, the RTNL (Routing Netlink) is not acquired before calling the ip[6]mr_free_table() function, leading to a potential use-after-free vulnerability. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service (DoS) condition. The vulnerability was introduced in version v4.0 of the Kernel and has been fixed in version v5.4.180.
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
If updating the Kernel is not immediately feasible, a possible workaround is to avoid triggering the failure path that leads to the vulnerable code. This can be achieved by ensuring that the conditions leading to the failure path are not met. However, this workaround may not provide complete protection and should be considered temporary until the Kernel is updated.
Conclusion
In conclusion, the Kernel is vulnerable to a use-after-free vulnerability in the ipmr and ip6mr modules. This vulnerability can be mitigated by updating the Kernel to version v5.4.180 or later. If immediate updating is not possible, a temporary workaround can be implemented. It is important to stay vigilant and promptly address vulnerabilities to ensure the security and stability of the system. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could potentially allow an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition on a system running the affected version of the Kernel.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to promptly update the Kernel to the fixed version to mitigate any potential risks.
While updating the Kernel is the recommended solution, you can also consider implementing the provided workaround to minimize the risk until the update can be applied. However, it is crucial to note that workarounds may not provide complete protection and should be seen as temporary measures.
For more detailed information about this vulnerability, including technical details and the specific commit that fixed it, you can refer to the vulnerability report at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1000xxx/GSD-2022-1000338.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
