CVE-2026-23080: can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak
In the Linux kernel, the following vulnerability has been resolved:
can: mcbausb: mcbausbreadbulkcallback(): fix URB memory leak
Fix similar memory leak as in commit 7352e1d5932a ("can: gsusb: gsusbreceivebulkcallback(): fix URB memory leak").
In mcbausbprobe() -> mcbausbstart(), the URBs for USB-in transfers are allocated, added to the priv->rxsubmitted anchor and submitted. In the complete callback mcbausbreadbulkcallback(), the URBs are processed and resubmitted. In mcbausbclose() -> mcbaurbunlink() the URBs are freed by calling usbkillanchoredurbs(&priv->rxsubmitted).
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 usbkillanchoredurbs().
Fix the memory leak by anchoring the URB in the mcbausbreadbulkcallback()to the priv->rxsubmitted anchor.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23080?
The severity of CVE-2026-23080 is medium, rated at 5.5 on the CVSS scale.
How do I fix CVE-2026-23080?
To fix CVE-2026-23080, you should apply the available patch from the Linux kernel.
What type of vulnerability is CVE-2026-23080?
CVE-2026-23080 is a memory leak vulnerability in the Linux kernel's mcba_usb driver.
Which Linux kernel versions are affected by CVE-2026-23080?
CVEs generally affect specific versions of the Linux kernel; it is essential to check your kernel version against the patch notes.
What is the impact of CVE-2026-23080?
The impact of CVE-2026-23080 is that it can lead to a memory leak, resulting in resource depletion over time.