CVE-2026-23061can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% 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: kvaser_usb: kvaser_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 kvaser_usb_set_{,data_}bittiming() -> kvaser_usb_setup_rx_urbs(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback kvaser_usb_read_bulk_callback(), the URBs are processed and resubmitted. In kvaser_usb_remove_interfaces() the URBs are freed by calling usb_kill_anchored_urbs(&dev->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 kvaser_usb_read_bulk_callback() to the dev->rx_submitted anchor.
Timeline
ID reserved
By Linux
- 22 days later
· 22 days later
Published
- 9 months later
· 9 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 · Modified | 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.17% · top 93% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 080f40a6fa28dab299da7a652e444b1e2d9231e7 – < d9d824582f2ec76459ffab449e9b05c7bc49645c
- affected 080f40a6fa28dab299da7a652e444b1e2d9231e7 – < 40a3334ffda479c63e416e61ff086485e24401f7
- affected 080f40a6fa28dab299da7a652e444b1e2d9231e7 – < c1b39fa24c140bc616f51fef4175c1743e2bb132
- affected 080f40a6fa28dab299da7a652e444b1e2d9231e7 – < 7c308f7530bffafa994e0aa8dc651a312f4b9ff4
- affected 080f40a6fa28dab299da7a652e444b1e2d9231e7 – < 94a7fc42e21c7d9d1c49778cd1db52de5df52a01
- affected 080f40a6fa28dab299da7a652e444b1e2d9231e7 – < 3b1a593eab941c3f32417896cc7df564191f2482
- affected 080f40a6fa28dab299da7a652e444b1e2d9231e7 – < 248e8e1a125fa875158df521b30f2cc7e27eeeaa
- affected 3.8
- unaffected < 3.8
- 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/d9d824582f2ec76459ffab449e9b05c7bc49645c (opens in a new tab)
- https://git.kernel.org/stable/c/40a3334ffda479c63e416e61ff086485e24401f7 (opens in a new tab)
- https://git.kernel.org/stable/c/c1b39fa24c140bc616f51fef4175c1743e2bb132 (opens in a new tab)
- https://git.kernel.org/stable/c/7c308f7530bffafa994e0aa8dc651a312f4b9ff4 (opens in a new tab)
- https://git.kernel.org/stable/c/94a7fc42e21c7d9d1c49778cd1db52de5df52a01 (opens in a new tab)
- https://git.kernel.org/stable/c/3b1a593eab941c3f32417896cc7df564191f2482 (opens in a new tab)
- https://git.kernel.org/stable/c/248e8e1a125fa875158df521b30f2cc7e27eeeaa (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-5483 (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-23061)Record last updated .