<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 22:06:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23108 — can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23108</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak&lt;/p&gt;
&lt;p&gt;Fix similar memory leak as in commit 7352e1d5932a (&amp;#34;can: gs_usb:
gs_usb_receive_bulk_callback(): fix URB memory leak&amp;#34;).&lt;/p&gt;
&lt;p&gt;In usb_8dev_open() -&amp;gt; usb_8dev_start(), the URBs for USB-in transfers are
allocated, added to the priv-&amp;gt;rx_submitted anchor and submitted. In the
complete callback usb_8dev_read_bulk_callback(), the URBs are processed and
resubmitted. In usb_8dev_close() -&amp;gt; unlink_all_urbs() the URBs are freed by
calling usb_kill_anchored_urbs(&amp;amp;priv-&amp;gt;rx_submitted).&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;Fix the memory leak by anchoring the URB in the
usb_8dev_read_bulk_callback() to the priv-&amp;gt;rx_submitted anchor.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak&lt;/p&gt;
&lt;p&gt;Fix similar memory leak as in commit 7352e1d5932a (&amp;#34;can: gs_usb:
gs_usb_receive_bulk_callback(): fix URB memory leak&amp;#34;).&lt;/p&gt;
&lt;p&gt;In usb_8dev_open() -&amp;gt; usb_8dev_start(), the URBs for USB-in transfers are
allocated, added to the priv-&amp;gt;rx_submitted anchor and submitted. In the
complete callback usb_8dev_read_bulk_callback(), the URBs are processed and
resubmitted. In usb_8dev_close() -&amp;gt; unlink_all_urbs() the URBs are freed by
calling usb_kill_anchored_urbs(&amp;amp;priv-&amp;gt;rx_submitted).&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;Fix the memory leak by anchoring the URB in the
usb_8dev_read_bulk_callback() to the priv-&amp;gt;rx_submitted anchor.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23108</guid>
    </item>
  </channel>
</rss>
