Resource Leak in zorro7xx_remove_one() in Kernel
Summary
GSD-2022-1001696: scsi: zorro7xx: Fix a resource leak in zorro7xx_remove_one(). Affects Kernel versions >= 45804fbb00eea27bdf4d62751681228a9e2844e9, < aefd755a96051aa56b198cb7ecd168b22ba384f6. 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 provides core functionality and interfaces with hardware devices. It manages system resources, including memory, processes, and input/output operations. The zorro7xx module in the Kernel is responsible for handling SCSI (Small Computer System Interface) devices connected via the Zorro bus on Amiga computers. The zorro7xx_remove_one() function is used to remove a zorro7xx device when it is no longer needed.
Vulnerability Detail
The zorro7xx_remove_one() function in the zorro7xx module of the Kernel has a resource leak vulnerability. When removing a zorro7xx device, the function fails to release certain resources, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory, causing a denial-of-service condition or other adverse effects. The vulnerability was introduced in version v2.6.23 of the Kernel and is fixed in version v5.15.34.
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 recommended to apply the fix by updating the Kernel to the latest version.
Conclusion
The zorro7xx_remove_one() function in the zorro7xx module of the Kernel has a resource leak vulnerability that can lead to memory exhaustion and other adverse effects. Users should update their Kernel to version v5.15.34 or later to fix this vulnerability. No known workarounds are available. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to a denial-of-service condition or other adverse effects by exhausting system memory.
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 and Vulert will analyze it for any open-source vulnerabilities, including this one.
No, this vulnerability requires local access to the system.
There are no known instances of this vulnerability being exploited in the wild.
For more details about this vulnerability, you can refer to the source information provided by the Cloud Security Alliance's GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001696.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
