Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43223media: pvrusb2: fix URB leak in pvr2_send_request_ex

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43223, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < da524c939b1e5ba17f10db4bde4bdaf569ffcda6
    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < cf459d6ffa5e150ef3744b897f936ff24b52bd15
    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < 77a63f8efc434ddb04667ed632aade58301a2f13
    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < 4ba5c7a1aade7090172cbffd4d120bf4cf5ccbde
    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < 58dd722b6c3debcddb4684fb256c90fee7f063e5
    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < 2011929f0e4cf6a0a34dd6205911b12276904453
    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < 5f3ac816861c3b8a5d1a3645b17dc3a99d668d94
    • affected d855497edbfbf9e19a17f4a1154bca69cb4bd9ba – < a8333c8262aed2aedf608c18edd39cf5342680a7
  • Linux · Linux

    • affected 2.6.18
    • unaffected < 2.6.18
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43223 badge
[![CVE-2026-43223](https://cveledger.app/badge/CVE-2026-43223.svg)](https://cveledger.app/cve/CVE-2026-43223)

Record last updated .