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-23080can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak

Description

In the Linux kernel, the following vulnerability has been resolved: can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In mcba_usb_probe() -> mcba_usb_start(), the URBs for USB-in transfers are allocated, added to the priv->rx_submitted anchor and submitted. In the complete callback mcba_usb_read_bulk_callback(), the URBs are processed and resubmitted. In mcba_usb_close() -> mcba_urb_unlink() the URBs are freed by calling usb_kill_anchored_urbs(&priv->rx_submitted). However, this does not take into account that the USB framework unanchors the URB before the complete function is called. This means that once an in-URB has been completed, it is no longer anchored and is ultimately not released in usb_kill_anchored_urbs(). Fix the memory leak by anchoring the URB in the mcba_usb_read_bulk_callback()to the priv->rx_submitted anchor.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 3 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-23080, 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.15% · top 96% of all CVEs (16 Nov 2026)
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 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 8b34c611a4feb81921bc4728c091e4e3ba0270c0
    • affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < b5a1ccdc63b71d93a69a6b72f7a3f3934293ea60
    • affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 59153b6388e05609144ad56a9b354e9100a91983
    • affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 179f6f0cf5ae489743273b7c1644324c0c477ea9
    • affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 94c9f6f7b953f6382fef4bdc48c046b861b8868f
    • affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < d374d715e338dfc3804aaa006fa6e470ffebb264
    • affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 710a7529fb13c5a470258ff5508ed3c498d54729
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .