CVE-2026-23082
Unknown Unknown - Not Provided
Memory Leak and Infinite Loop in Linux gs_usb CAN Driver

Publication date: 2026-02-04

Last updated on: 2026-04-18

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error In commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"), the URB was re-anchored before usb_submit_urb() in gs_usb_receive_bulk_callback() to prevent a leak of this URB during cleanup. However, this patch did not take into account that usb_submit_urb() could fail. The URB remains anchored and usb_kill_anchored_urbs(&parent->rx_submitted) in gs_can_close() loops infinitely since the anchor list never becomes empty. To fix the bug, unanchor the URB when an usb_submit_urb() error occurs, also print an info message.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-04
Last Modified
2026-04-18
Generated
2026-05-07
AI Q&A
2026-02-04
EPSS Evaluated
2026-05-05
NVD
CVE-2026-23082
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
linux linux_kernel 6.19
linux linux_kernel 6.12.67
linux linux_kernel 6.18.7
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-835 The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's gs_usb driver, specifically in the function gs_usb_receive_bulk_callback(). A previous patch intended to fix a memory leak by re-anchoring a USB Request Block (URB) before calling usb_submit_urb() did not handle the case where usb_submit_urb() fails. When such a failure occurs, the URB remains anchored, causing the function usb_kill_anchored_urbs() to loop infinitely because the anchor list never empties.

The issue was fixed by ensuring that the URB is unanchored if usb_submit_urb() returns an error, preventing the infinite loop and associated resource management problems.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to enter an infinite loop during cleanup operations related to USB communication in the gs_usb driver. This can lead to system instability or a denial of service condition because the kernel is stuck in a loop trying to kill anchored URBs that never get unanchored.

Additionally, the improper handling of URBs could potentially lead to resource leaks, which might degrade system performance over time.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart