<?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>Wed, 30 Sep 2026 03:34:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40315 — usb: gadget: f_fs: Fix epfile null pointer access after ep enable.</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40315</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: Fix epfile null pointer access after ep enable.&lt;/p&gt;
&lt;p&gt;A race condition occurs when ffs_func_eps_enable() runs concurrently
with ffs_data_reset(). The ffs_data_clear() called in ffs_data_reset()
sets ffs-&amp;gt;epfiles to NULL before resetting ffs-&amp;gt;eps_count to 0, leading
to a NULL pointer dereference when accessing epfile-&amp;gt;ep in
ffs_func_eps_enable() after successful usb_ep_enable().&lt;/p&gt;
&lt;p&gt;The ffs-&amp;gt;epfiles pointer is set to NULL in both ffs_data_clear() and
ffs_data_close() functions, and its modification is protected by the
spinlock ffs-&amp;gt;eps_lock. And the whole ffs_func_eps_enable() function
is also protected by ffs-&amp;gt;eps_lock.&lt;/p&gt;
&lt;p&gt;Thus, add NULL pointer handling for ffs-&amp;gt;epfiles in the
ffs_func_eps_enable() function to fix issues&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: Fix epfile null pointer access after ep enable.&lt;/p&gt;
&lt;p&gt;A race condition occurs when ffs_func_eps_enable() runs concurrently
with ffs_data_reset(). The ffs_data_clear() called in ffs_data_reset()
sets ffs-&amp;gt;epfiles to NULL before resetting ffs-&amp;gt;eps_count to 0, leading
to a NULL pointer dereference when accessing epfile-&amp;gt;ep in
ffs_func_eps_enable() after successful usb_ep_enable().&lt;/p&gt;
&lt;p&gt;The ffs-&amp;gt;epfiles pointer is set to NULL in both ffs_data_clear() and
ffs_data_close() functions, and its modification is protected by the
spinlock ffs-&amp;gt;eps_lock. And the whole ffs_func_eps_enable() function
is also protected by ffs-&amp;gt;eps_lock.&lt;/p&gt;
&lt;p&gt;Thus, add NULL pointer handling for ffs-&amp;gt;epfiles in the
ffs_func_eps_enable() function to fix issues&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40315</guid>
    </item>
  </channel>
</rss>
