CVE-2026-23108None▾ SunlitIn the Linux kernel, the following vulnerability has been resolved: can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix …
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Oct 19.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.1%
0.1% → 0.2%
In the Linux kernel, the following vulnerability has been resolved:
can: usb_8dev: usb_8dev_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 usb_8dev_open() -> usb_8dev_start(), the URBs for USB-in transfers are allocated, added to the priv->rx_submitted anchor and submitted. In the complete callback usb_8dev_read_bulk_callback(), the URBs are processed and resubmitted. In usb_8dev_close() -> unlink_all_urbs() 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 usb_8dev_read_bulk_callback() to the priv->rx_submitted anchor.
Linux >= 0024d8ad1639e32d717445c69ca813fd19c2a91c < feb8243eaea7efd5279b19667d7189fd8654c87aLinux >= 0024d8ad1639e32d717445c69ca813fd19c2a91c < ef6e608e5ee71eca0cd3475c737e684cef24f240Linux >= 0024d8ad1639e32d717445c69ca813fd19c2a91c < 60719661b4cbd7ffbed1a0e0fa3bbc82d8bd2be9Linux >= 0024d8ad1639e32d717445c69ca813fd19c2a91c < 59ff56992bba28051ad67cd8cc7b0edfe7280796Linux >= 0024d8ad1639e32d717445c69ca813fd19c2a91c < ea4a98e924164586066b39f29bfcc7cc9da108cdLinux >= 0024d8ad1639e32d717445c69ca813fd19c2a91c < 07e9373739c6388af9d99797cdb2e79dbbcbe92bLinux >= 0024d8ad1639e32d717445c69ca813fd19c2a91c < f7a980b3b8f80fe367f679da376cf76e800f9480Linux 3.9Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets