CVE-2022-49982: media: pvrusb2: fix memory leak in pvr_probe
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2fe46195d2f0d5d09ea65433aefe47a4d0d0ff4d, 466b67c0543b2ae67814d053f6e29b39be6b33bb, 491762b3250fb06a0c97b5198656ea48359eaeed.
Low priority for now. Upgrade to Linux Linux 2fe46195d2f0d5d09ea65433aefe47a4d0d0ff4d, 466b67c0543b2ae67814d053f6e29b39be6b33bb, 491762b3250fb06a0c97b5198656ea48359eaeed or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix memory leak in pvr_probe The error handling code in pvr2_hdw_create forgets to unregister the v4l2 device. When pvr2_hdw_create returns back to pvr2_context_create, it calls pvr2_context_destroy to destroy context, but mp->hdw is NULL, which leads to that pvr2_hdw_destroy directly returns. Fix this by adding v4l2_device_unregister to decrease the refcount of usb interface.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.9.327
- linux linux kernel4.10 and later · before 4.14.292
- linux linux kernel4.15 and later · before 4.19.257
- linux linux kernel4.20 and later · before 5.4.212
- linux linux kernel5.5 and later · before 5.10.141
- linux linux kernel5.11 and later · before 5.15.65
- linux linux kernel5.16 and later · before 5.19.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.30affected
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before 2fe46195d2f0d5d09ea65433aefe47a4d0d0ff4daffected · git
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before ba7dd8a9686a61a34b3a7b922ce721378d4740d0affected · git
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before 491762b3250fb06a0c97b5198656ea48359eaeedaffected · git
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before 466b67c0543b2ae67814d053f6e29b39be6b33bbaffected · git
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before bacb37bdc2a21c8f7fdc83dcc0dea2f4ca1341fbaffected · git
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before f2f6e67522916f53ad8ccd4dbe68dcf76e9776e5affected · git
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before c02d2a91a85c4c4d05826cd1ea74a9b8d42e4280affected · git
- b72b7bf5cbb2ae77b3bf748456655fc284baf04c and later · before 945a9a8e448b65bec055d37eba58f711b39f66f0affected · git
- before 2.6.30not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.2-1 | 6.0.2-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49980Jun 18, 2025 · USB: gadget: Fix use-after-free Read in usb_udc_uevent()31Monitor
- ← EarlierCVE-2022-49981Jun 18, 2025 · HID: hidraw: fix memory leak in hidraw_release()22Monitor
- Later →CVE-2022-49983Jun 18, 2025 · udmabuf: Set the DMA mask for the udmabuf device (v2)22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2fe46195d2f0d5d09ea65433aefe47a4d0d0ff4d | Vendor (CNA) |
| Linux Linux | 466b67c0543b2ae67814d053f6e29b39be6b33bb | Vendor (CNA) |
| Linux Linux | 491762b3250fb06a0c97b5198656ea48359eaeed | Vendor (CNA) |
| Linux Linux | 945a9a8e448b65bec055d37eba58f711b39f66f0 | Vendor (CNA) |
| Linux Linux | ba7dd8a9686a61a34b3a7b922ce721378d4740d0 | Vendor (CNA) |
| Linux Linux | bacb37bdc2a21c8f7fdc83dcc0dea2f4ca1341fb | Vendor (CNA) |
| Linux Linux | c02d2a91a85c4c4d05826cd1ea74a9b8d42e4280 | Vendor (CNA) |
| Linux Linux | f2f6e67522916f53ad8ccd4dbe68dcf76e9776e5 | Vendor (CNA) |
| debian:linux | 6.0.2-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/466b67c0543b2ae67814d053f6e29b39be6b33bb
- git.kernel.org/stable/c/491762b3250fb06a0c97b5198656ea48359eaeed
- git.kernel.org/stable/c/945a9a8e448b65bec055d37eba58f711b39f66f0
- git.kernel.org/stable/c/ba7dd8a9686a61a34b3a7b922ce721378d4740d0
- git.kernel.org/stable/c/bacb37bdc2a21c8f7fdc83dcc0dea2f4ca1341fb
- git.kernel.org/stable/c/c02d2a91a85c4c4d05826cd1ea74a9b8d42e4280
- git.kernel.org/stable/c/f2f6e67522916f53ad8ccd4dbe68dcf76e9776e5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.