Memory leaks in nexthop notification chain listeners in Kernel
Summary
GSD-2021-1001753: nexthop: Fix memory leaks in nexthop notification chain listeners. Affects Kernel versions >= 2a014b200bbd973cc96e082a5bc445fe20b50f32, < 741760fa6252628a3d3afad439b72437d4b123d9. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a critical component of the Linux operating system that manages system resources and provides an interface for applications to interact with the hardware. It is responsible for tasks such as process management, memory management, and device drivers. The nexthop feature in the Kernel allows for efficient routing decisions by providing a mechanism to specify the next hop for network traffic. However, a vulnerability has been discovered in the nexthop notification chain listeners, which can lead to memory leaks.
Vulnerability Detail
The vulnerability in the nexthop notification chain listeners arises from a memory leak issue. When certain events occur, such as changes in the nexthop configuration, the listeners may not properly release allocated memory, resulting in memory leaks. This can lead to a gradual depletion of system resources, potentially causing performance degradation or even system instability. The vulnerability was introduced in Kernel version v5.11 and has been fixed in version v5.14.9.
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
There is no specific workaround available for this vulnerability. However, users can mitigate the risk by closely monitoring system resources and taking appropriate actions if signs of resource depletion or instability are observed.
Conclusion
The memory leaks in nexthop notification chain listeners in the Kernel can lead to resource depletion and system instability. It is crucial to update the Linux Kernel to version v5.14.9 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory leaks, which can gradually deplete system resources and potentially cause performance degradation or system instability.
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 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 exploitation in the future.
Yes, it is possible to manually patch the Kernel source code to fix this vulnerability. However, this requires advanced knowledge of the Kernel internals and is not recommended for inexperienced users. It is safer and more convenient to update to the latest Kernel version that includes the fix.
You can find more information about this vulnerability in the official Linux Kernel repository. The commit history and release notes provide detailed information about the fix and its impact.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
