Refcount Leak in cleanup_dev() in char: xillybus
Summary
GSD-2022-1002552: char: xillybus: fix a refcount leak in cleanup_dev(). Affects Kernel versions < e277b95acdab84cd5d2f8d537a37aef6d21e988b. 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 char: xillybus package is a component of the Linux Kernel ecosystem. It provides support for Xillybus IP cores, which are used for communication between FPGA and software. The package allows for easy integration of FPGA-based devices into Linux systems. However, a vulnerability has been discovered in the cleanup_dev() function of the package.
Vulnerability Detail
The vulnerability in cleanup_dev() function of char: xillybus package leads to a refcount leak. This means that the reference count of a resource is not properly decremented, resulting in a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory, leading to denial of service or other malicious activities. The vulnerability has been fixed in Linux Kernel version v5.18.4 by commit e277b95acdab84cd5d2f8d537a37aef6d21e988b.
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 mentioned for this vulnerability.
Conclusion
In conclusion, the refcount leak vulnerability in the cleanup_dev() function of char: xillybus package can be fixed by updating the Linux Kernel to version v5.18.4 or later. It is important to apply this fix to prevent potential memory leaks and malicious activities. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could be exploited by an attacker to exhaust system memory, leading to denial of service or other malicious activities.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for any open-source vulnerabilities, including this one.
Yes, the vulnerability has been fixed in Linux Kernel version v5.18.4 by commit e277b95acdab84cd5d2f8d537a37aef6d21e988b. It is recommended to update to this version or later to apply the fix.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to prevent any potential attacks.
You can find more information about this vulnerability in the official Linux Kernel repository. The commit e277b95acdab84cd5d2f8d537a37aef6d21e988b provides detailed information about the fix.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
