Service interruption via pvrusb2 probe memory leak
Published Jun 18, 2025 · Updated May 11, 2026
Memory leak in the Linux pvrusb2 driver allows local users to interrupt service by triggering a failed USB device probe. The pvr2_hdw_create error path registers a V4L2 device but does not unregister it, while later cleanup returns early because mp->hdw is NULL and retains the USB interface reference. Exploitation requires local low-privileged access and a pvrusb2 probe failure; the resulting leak affects availability without reported data disclosure or modification.
Summary
What happened
Memory leak in the Linux pvrusb2 driver allows local users to interrupt service by triggering a failed USB device probe. The pvr2_hdw_create error path registers a V4L2 device but does not unregister it, while later cleanup returns early because mp->hdw is NULL and retains the USB interface reference. Exploitation requires local low-privileged access and a pvrusb2 probe failure; the resulting leak affects availability without reported data disclosure or modification.
The record
- CVE
- CVE-2022-49982
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.30
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <2fe46195d2f0d5d09ea65433aefe47a4d0d0ff4d
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <466b67c0543b2ae67814d053f6e29b39be6b33bb
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <491762b3250fb06a0c97b5198656ea48359eaeed
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <945a9a8e448b65bec055d37eba58f711b39f66f0
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <ba7dd8a9686a61a34b3a7b922ce721378d4740d0
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <bacb37bdc2a21c8f7fdc83dcc0dea2f4ca1341fb
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <c02d2a91a85c4c4d05826cd1ea74a9b8d42e4280
- Affected versionversion=b72b7bf5cbb2ae77b3bf748456655fc284baf04c <f2f6e67522916f53ad8ccd4dbe68dcf76e9776e5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo