<?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 12:48:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41049 — filelock: fix potential use-after-free in posix_lock_inode</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-41049</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;filelock: fix potential use-after-free in posix_lock_inode&lt;/p&gt;
&lt;p&gt;Light Hsieh reported a KASAN UAF warning in trace_posix_lock_inode().
The request pointer had been changed earlier to point to a lock entry
that was added to the inode&amp;#39;s list. However, before the tracepoint could
fire, another task raced in and freed that lock.&lt;/p&gt;
&lt;p&gt;Fix this by moving the tracepoint inside the spinlock, which should
ensure that this doesn&amp;#39;t happen.&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;filelock: fix potential use-after-free in posix_lock_inode&lt;/p&gt;
&lt;p&gt;Light Hsieh reported a KASAN UAF warning in trace_posix_lock_inode().
The request pointer had been changed earlier to point to a lock entry
that was added to the inode&amp;#39;s list. However, before the tracepoint could
fire, another task raced in and freed that lock.&lt;/p&gt;
&lt;p&gt;Fix this by moving the tracepoint inside the spinlock, which should
ensure that this doesn&amp;#39;t happen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-41049</guid>
    </item>
  </channel>
</rss>
