CVE-2026-23061: Linux kernel · can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d9d824582f2ec76459ffab449e9b05c7bc49645c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in d9d824582f2ec76459ffab449e9b05c7bc49645c, c1b39fa24c140bc616f51fef4175c1743e2bb132, 248e8e1a125fa875158df521b30f2cc7e27eeeaa +4
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/d9d824582f2ec76459ffab449e9b05c7bc49645c (opens in a new tab)
- git.kernel.org/stable/c/40a3334ffda479c63e416e61ff086485e24401f7 (opens in a new tab)
- git.kernel.org/stable/c/c1b39fa24c140bc616f51fef4175c1743e2bb132 (opens in a new tab)
- git.kernel.org/stable/c/7c308f7530bffafa994e0aa8dc651a312f4b9ff4 (opens in a new tab)
- git.kernel.org/stable/c/94a7fc42e21c7d9d1c49778cd1db52de5df52a01 (opens in a new tab)
- git.kernel.org/stable/c/3b1a593eab941c3f32417896cc7df564191f2482 (opens in a new tab)
- git.kernel.org/stable/c/248e8e1a125fa875158df521b30f2cc7e27eeeaa (opens in a new tab)