Memory Leak Vulnerability in yam Package
Summary
GSD-2022-1000104: yam: fix a memory leak in yam_siocdevprivate(). Affects Kernel versions >= d0539c56391d449603f7ff2bcddf38995df49749, < 4bbdfb71d2898a9d6e777a948a7484903a4ad2c3. 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 yam package is a component of the Linux Kernel, which is responsible for managing network interfaces. It provides functionality for configuring and controlling network devices. The vulnerability in question, identified as GSD-2022-1000104, is a memory leak issue that occurs in the yam_siocdevprivate() function. This function is responsible for handling private ioctl requests for the yam network driver.
Vulnerability Detail
The memory leak vulnerability in yam_siocdevprivate() can be exploited by an attacker to exhaust system memory resources. By repeatedly triggering the vulnerable function, an attacker can cause a gradual depletion of available memory, leading to system instability or denial of service. This vulnerability was introduced in version v4.14.79 of the Linux Kernel and has been fixed in version v4.14.265.
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 known workaround for this vulnerability. It is essential to apply the fix by updating the Linux Kernel to a version that includes the necessary patch.
Conclusion
The memory leak vulnerability in the yam package can be a serious issue, leading to system instability or denial of service. It is crucial to update the Linux Kernel to a fixed version to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory exhaustion, causing system instability or denial of service.
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 the dependencies and alert you if any known vulnerabilities are present.
At the time of this report, there is no known public exploit for this vulnerability. However, it is still crucial to apply the fix to prevent potential attacks.
No, this vulnerability requires local access to the system in order to trigger the vulnerable function and exploit the memory leak.
The only effective mitigation is to update the Linux Kernel to a version that includes the fix for this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
