Array Index Out-of-Bounds Vulnerability in media: pvrusb2
Summary
GSD-2022-1004073: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init. Affects Kernel versions >= d855497edbfbf9e19a17f4a1154bca69cb4bd9ba, < 4351bfe36aba9fa7dc9d68d498d25d41a0f45e67. 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 is responsible for handling various media devices, such as video capture cards. One of the components within this package is pvrusb2, which provides support for Hauppauge PVR USB 2.0 devices. These devices allow users to capture and record video content. However, a vulnerability has been discovered in the pvr2_i2c_core_init function, which can lead to an array index out-of-bounds error.
Vulnerability Detail
The vulnerability arises due to improper bounds checking in the pvr2_i2c_core_init function of the pvrusb2 component. An attacker could exploit this flaw by sending specially crafted input to the affected device, triggering the out-of-bounds access. This could potentially result in memory corruption, leading to a system crash or the execution of arbitrary code with kernel privileges. The vulnerability was introduced in version 2.6.18 of the Linux Kernel and has been fixed in version 4.9.318.
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 or disconnect the affected Hauppauge PVR USB 2.0 devices until the Linux Kernel is updated to a fixed version. This will help mitigate the risk of exploitation through this specific vulnerability.
Conclusion
In conclusion, the array index out-of-bounds vulnerability in the media: pvrusb2 component of the Linux Kernel can potentially lead to memory corruption and the execution of arbitrary code with kernel privileges. It is crucial to update the Linux Kernel to version 4.9.318 or later to mitigate this vulnerability. Additionally, regular system updates and monitoring for new vulnerabilities are recommended. For further assistance or support in addressing this vulnerability, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially allow an attacker to execute arbitrary code with kernel privileges or cause a system crash, leading to a denial-of-service condition.
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 the Vulert service will analyze it for any known vulnerabilities.
At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is always recommended to apply security patches and updates as soon as they become available to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected device is accessible over a network. An attacker could send specially crafted input to trigger the vulnerability and potentially gain unauthorized access or disrupt the system.
For more detailed information about this vulnerability, including technical details and the specific code changes made to fix it, you can refer to the vulnerability report on the Cloud Security Alliance's GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004073.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
