<?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://cve.radiocsirt.org</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, 06 Oct 2026 22:15:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49661 — can: gs_usb: gs_usb_open/close(): fix memory leak</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49661</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: gs_usb: gs_usb_open/close(): fix memory leak&lt;/p&gt;
&lt;p&gt;The gs_usb driver appears to suffer from a malady common to many USB
CAN adapter drivers in that it performs usb_alloc_coherent() to
allocate a number of USB request blocks (URBs) for RX, and then later
relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t
actually free them. As a result, this may be leaking DMA memory that&amp;#39;s
been used by the driver.&lt;/p&gt;
&lt;p&gt;This commit is an adaptation of the techniques found in the esd_usb2
driver where a similar design pattern led to a memory leak. It
explicitly frees the RX URBs and their DMA memory via a call to
usb_free_coherent(). Since the RX URBs were allocated in the
gs_can_open(), we remove them in gs_can_close() rather than in the
disconnect function as was done in esd_usb2.&lt;/p&gt;
&lt;p&gt;For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory
leak&amp;#34;).&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: gs_usb: gs_usb_open/close(): fix memory leak&lt;/p&gt;
&lt;p&gt;The gs_usb driver appears to suffer from a malady common to many USB
CAN adapter drivers in that it performs usb_alloc_coherent() to
allocate a number of USB request blocks (URBs) for RX, and then later
relies on usb_kill_anchored_urbs() to free them, but this doesn&amp;#39;t
actually free them. As a result, this may be leaking DMA memory that&amp;#39;s
been used by the driver.&lt;/p&gt;
&lt;p&gt;This commit is an adaptation of the techniques found in the esd_usb2
driver where a similar design pattern led to a memory leak. It
explicitly frees the RX URBs and their DMA memory via a call to
usb_free_coherent(). Since the RX URBs were allocated in the
gs_can_open(), we remove them in gs_can_close() rather than in the
disconnect function as was done in esd_usb2.&lt;/p&gt;
&lt;p&gt;For more information, see the 928150fad41b (&amp;#34;can: esd_usb2: fix memory
leak&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49661</guid>
    </item>
  </channel>
</rss>
