dbcve.org
Linux KernelOperating system · Linux

CVE-2026-43223

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 5.10.252 / 5.15.202 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix URB leak in pvr2_send_request_ex When pvr2_send_request_ex() submits a write URB successfully but fails to submit the read URB (e.g. returns -ENOMEM), it returns immediately without waiting for the write URB to complete. Since the driver reuses the same URB structure, a subsequent call to pvr2_send_request_ex() attempts to submit the still-active write URB, triggering a 'URB submitted while active' warning in usb_submit_urb(). Fix this by ensuring the write URB is unlinked and waited upon if the read URB submission fails.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-401

Allocated memory is never released on some path, so a long-running service or a repeatedly triggered request steadily consumes memory until performance degrades or the process crashes. Attackers exploit it by simply driving the leaking path. Remediation is pairing every allocation with a release and using ownership patterns or tooling to catch what leaks.

General guidance for the memory leak class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 2.6.18, < 5.10.252>= 5.11, < 5.15.202>= 5.16, < 6.1.165>= 6.2, < 6.6.128>= 6.7, < 6.12.75>= 6.13, < 6.18.16>= 6.19, < 6.19.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.252 / 5.15.202 / 6.1.165 or later
Fixed in 5.10.2525.15.2026.1.165
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 5.10.252, 5.15.202, 6.1.165, or 6.6.128 (or later stable releases within your major version branch)

  1. Identify the current running kernel version using `uname -r`
  2. Check which version range your current kernel falls into (>= 2.6.18, < 5.10.252; >= 5.11, < 5.15.202; >= 5.16, < 6.1.165; or >= 6.2, < 6.6.128)
  3. If using a distribution-provided kernel, check for available updates via your package manager (e.g., `apt update && apt upgrade` for Debian/Ubuntu, `yum update` for RHEL/CentOS, or `dnf upgrade` for Fedora)
  4. If using a custom-built kernel, obtain the patch from the commit URL: https://git.kernel.org/stable/c/2011929f0e4cf6a0a34dd6205911b12276904453
  5. Apply the patch to the pvrusb2 driver source code (drivers/media/usb/pvrusb2/pvrusb2-hdw.c) and rebuild the kernel
  6. Reboot into the updated kernel and verify the fix using `dmesg` to confirm no 'URB submitted while active' warnings appear
Caveat Upgrading kernel versions may require rebuilding out-of-tree kernel modules; ensure driver compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-43223 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data