Vulnerability in Kernel package: media: usb: go7007: s2250-board: fix leak in probe()
Summary
GSD-2022-1001572: media: usb: go7007: s2250-board: fix leak in probe(). Affects Kernel versions >= d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2, < b5470f3efa530b10296257bb578ce4b1769e9a04. 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 package is a fundamental component of the Linux operating system, responsible for managing the system's core functionality. It provides essential services and functions to enable the interaction between hardware and software. The media subsystem within the Kernel handles various media-related operations, including USB devices. One of the components in this subsystem is the go7007 driver, which supports the Go7007 USB video capture device. The s2250-board module is a specific board implementation for the go7007 driver. This vulnerability affects the s2250-board module and can potentially impact systems utilizing the Go7007 USB video capture device.
Vulnerability Detail
The vulnerability in the s2250-board module of the go7007 driver arises from a memory leak issue in the probe() function. When the module is probed, it fails to release allocated memory in certain scenarios, leading to a memory leak. This vulnerability can be exploited by an attacker to exhaust system memory resources, potentially causing system instability or denial of service. The impact and attack plausibility of this vulnerability have not been proven yet.
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
The vulnerability in the s2250-board module of the go7007 driver can potentially lead to system instability or denial of service. It is crucial to update the Linux Kernel to version v5.16.19 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can potentially lead to system instability or denial of service due to memory exhaustion.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your manifest file, such as package-lock.json, without requiring access to the code or installation.
No, there is no known exploit for this vulnerability at the moment.
No, this vulnerability was introduced in version v3.10 of the Linux Kernel and fixed in version v5.16.19.
For more details about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
