Array Index Out-of-Bounds Vulnerability in media: pvrusb2

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003606: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init. Affects Kernel versions >= d855497edbfbf9e19a17f4a1154bca69cb4bd9ba, < a3304766d9384886e6d3092c776273526947a2e9. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The media package in the Linux Kernel is responsible for handling 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 initializes the I2C subsystem for communication with the device. 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 array index out-of-bounds vulnerability in pvr2_i2c_core_init occurs when accessing an array beyond its bounds. This can be exploited by an attacker to read or write data outside the intended memory region, potentially leading to information disclosure or arbitrary code execution. The vulnerability was introduced in version v2.6.18 of the Linux Kernel and has been fixed in version v5.10.121. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.121 or later. This can be done by applying the commit a3304766d9384886e6d3092c776273526947a2e9. Ensure that the updated Kernel is properly tested and deployed in the affected systems.

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 essential to update the Linux Kernel to the fixed version.

Conclusion

The array index out-of-bounds vulnerability in the pvrusb2 driver of the media package in the Linux Kernel can potentially lead to information disclosure or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.10.121 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can vary depending on the attacker's capabilities and the system's configuration. It could potentially lead to information disclosure or arbitrary code execution.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the playground will analyze it for vulnerabilities.

At the time of this report, there are no known exploits for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate the risk.

The exact attack vector for this vulnerability is not yet known. It is advisable to assume that remote exploitation is possible until further information is available.

For more details about this vulnerability, you can refer to the source link provided in the database_specific section of this report.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.121 or later. This can be done by applying the commit a3304766d9384886e6d3092c776273526947a2e9. Ensure that the updated Kernel is properly tested and deployed in the affected systems.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.