CVE-2026-23080can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak
- 5.5MediumCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
ID reserved
By Linux
- 22 days later
· 22 days later
Published
- 3 months later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS: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)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 8b34c611a4feb81921bc4728c091e4e3ba0270c0
- affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < b5a1ccdc63b71d93a69a6b72f7a3f3934293ea60
- affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 59153b6388e05609144ad56a9b354e9100a91983
- affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 179f6f0cf5ae489743273b7c1644324c0c477ea9
- affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 94c9f6f7b953f6382fef4bdc48c046b861b8868f
- affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < d374d715e338dfc3804aaa006fa6e470ffebb264
- affected 51f3baad7de943780ce0c17bd7975df567dd6e14 – < 710a7529fb13c5a470258ff5508ed3c498d54729
- 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
- https://git.kernel.org/stable/c/8b34c611a4feb81921bc4728c091e4e3ba0270c0 (opens in a new tab)
- https://git.kernel.org/stable/c/b5a1ccdc63b71d93a69a6b72f7a3f3934293ea60 (opens in a new tab)
- https://git.kernel.org/stable/c/59153b6388e05609144ad56a9b354e9100a91983 (opens in a new tab)
- https://git.kernel.org/stable/c/179f6f0cf5ae489743273b7c1644324c0c477ea9 (opens in a new tab)
- https://git.kernel.org/stable/c/94c9f6f7b953f6382fef4bdc48c046b861b8868f (opens in a new tab)
- https://git.kernel.org/stable/c/d374d715e338dfc3804aaa006fa6e470ffebb264 (opens in a new tab)
- https://git.kernel.org/stable/c/710a7529fb13c5a470258ff5508ed3c498d54729 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-5463 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-23080)Record last updated .