Acquire RTNL before calling ip[6]mr_free_table() on failure path in Kernel
Summary
GSD-2022-1000301: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path. Affects Kernel versions >= f243e5a7859a24d10975afb9a1708cac624ba6f1, < b541845dfc4e7df551955e70deec0921d6b297c3. 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 critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and ensures the stability and security of the system. The ipmr and ip6mr modules in the Kernel handle multicast routing tables for IPv4 and IPv6 respectively. These modules allow for efficient routing of multicast traffic across networks. However, a vulnerability has been identified in these modules that can lead to a denial-of-service (DoS) condition.
Vulnerability Detail
The vulnerability arises from a failure to acquire the RTNL (Routing Netlink) lock before calling the ip[6]mr_free_table() function on a failure path. This can result in a race condition where multiple threads or processes attempt to free the same multicast routing table concurrently, leading to memory corruption and system instability. An attacker could potentially exploit this vulnerability to crash the system or cause other adverse effects.
How To Fix
No fixed version is published for this vulnerability.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.14.267 or later. This fix ensures that the RTNL lock is acquired before calling ip[6]mr_free_table() on the failure path, preventing the race condition and potential memory corruption. Users should update their Kernel installation using the appropriate package manager or by manually compiling and installing the updated Kernel source code.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, users can disable the ipmr and ip6mr modules if they are not required for their specific use case. This can be done by blacklisting the modules or removing them from the Kernel configuration. However, this workaround may impact the functionality of multicast routing in certain scenarios, so it is recommended to apply the official fix as soon as possible.
Conclusion
In conclusion, the Kernel is vulnerable to a race condition in the ipmr and ip6mr modules, which can lead to a denial-of-service (DoS) condition. It is crucial to update the Kernel to version v4.14.267 or later to fix this vulnerability. Users can also check if their system is affected using the Vulert Playground. Applying the official fix or disabling the affected modules temporarily are recommended steps to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service (DoS) condition, potentially crashing the system or causing other adverse effects.
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 the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to prevent any potential attacks.
As a temporary workaround, you can disable the ipmr and ip6mr modules if they are not required for your specific use case. However, it is recommended to apply the official fix by updating the Kernel to the latest version.
You can find more information about this vulnerability in the GSD-2022-1000301 entry of the GSD database maintained by the Cloud Security Alliance. The link to the entry is available in the references section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.