Array Index Out-of-Bounds Vulnerability in media: pvrusb2
Summary
GSD-2022-1003802: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init. Affects Kernel versions >= d855497edbfbf9e19a17f4a1154bca69cb4bd9ba, < 1310fc3538dcc375a2f46ef0a438512c2ca32827. 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 media package in the Linux Kernel provides support for various media devices, including video capture cards. One such device is pvrusb2, which is used for capturing video from Pinnacle PCTV USB devices. The pvrusb2 driver in the media package handles the initialization of the I2C subsystem for these devices. However, a vulnerability exists in the pvr2_i2c_core_init function, which can lead to an array index out-of-bounds error.
Vulnerability Detail
The vulnerability occurs due to improper bounds checking in the pvr2_i2c_core_init function. An attacker can exploit this vulnerability by sending specially crafted input to the affected system, potentially leading to memory corruption or arbitrary code execution. The impact of this vulnerability depends on the attacker's capabilities and the context in which the vulnerable code is executed. It is important to note that this vulnerability has not been proven to be exploitable in the wild.
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
As a temporary workaround, users can disable the pvrusb2 driver if it is not required for their system. This can be done by blacklisting the pvrusb2 module or removing it from the kernel configuration. However, this workaround may result in the loss of functionality provided by the pvrusb2 driver.
Conclusion
The array index out-of-bounds vulnerability in the media: pvrusb2 driver can potentially lead to memory corruption or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.4.198 or later to mitigate this vulnerability. Users can also check their systems for vulnerabilities using the Vulert Playground (https://vulert.com/scanner). For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability depends on the attacker's capabilities and the context in which the vulnerable code is executed. It could potentially lead to memory corruption or arbitrary code execution.
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, there is currently no known exploit for this vulnerability. However, it is still important to apply the necessary updates to mitigate the risk.
As a temporary workaround, you can disable the pvrusb2 driver if it is not required for your system. However, it is recommended to update the Linux Kernel to the latest version to fully address the vulnerability.
You can refer to the vulnerability details in the GSD-2022-1003802.json file available in the GSD database (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
