<?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>Thu, 08 Oct 2026 13:13:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49755 — usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49755</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;usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait&lt;/p&gt;
&lt;p&gt;While performing fast composition switch, there is a possibility that the
process of ffs_ep0_write/ffs_ep0_read get into a race condition
due to ep0req being freed up from functionfs_unbind.&lt;/p&gt;
&lt;p&gt;Consider the scenario that the ffs_ep0_write calls the ffs_ep0_queue_wait
by taking a lock &amp;amp;ffs-&amp;gt;ev.waitq.lock. However, the functionfs_unbind isn&amp;#39;t
bounded so it can go ahead and mark the ep0req to NULL, and since there
is no NULL check in ffs_ep0_queue_wait we will end up in use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by making a serialized execution between the two functions using
a mutex_lock(ffs-&amp;gt;mutex).&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;usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait&lt;/p&gt;
&lt;p&gt;While performing fast composition switch, there is a possibility that the
process of ffs_ep0_write/ffs_ep0_read get into a race condition
due to ep0req being freed up from functionfs_unbind.&lt;/p&gt;
&lt;p&gt;Consider the scenario that the ffs_ep0_write calls the ffs_ep0_queue_wait
by taking a lock &amp;amp;ffs-&amp;gt;ev.waitq.lock. However, the functionfs_unbind isn&amp;#39;t
bounded so it can go ahead and mark the ep0req to NULL, and since there
is no NULL check in ffs_ep0_queue_wait we will end up in use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by making a serialized execution between the two functions using
a mutex_lock(ffs-&amp;gt;mutex).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49755</guid>
    </item>
  </channel>
</rss>
