<?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>Mon, 05 Oct 2026 15:15:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46690 — nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46690</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;nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease&lt;/p&gt;
&lt;p&gt;It is not safe to dereference fl-&amp;gt;c.flc_owner without first confirming
fl-&amp;gt;fl_lmops is the expected manager.  nfsd4_deleg_getattr_conflict()
tests fl_lmops but largely ignores the result and assumes that flc_owner
is an nfs4_delegation anyway.  This is wrong.&lt;/p&gt;
&lt;p&gt;With this patch we restore the &amp;#34;!= &amp;amp;nfsd_lease_mng_ops&amp;#34; case to behave
as it did before the change mentioned below.  This is the same as the
current code, but without any reference to a possible delegation.&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;nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease&lt;/p&gt;
&lt;p&gt;It is not safe to dereference fl-&amp;gt;c.flc_owner without first confirming
fl-&amp;gt;fl_lmops is the expected manager.  nfsd4_deleg_getattr_conflict()
tests fl_lmops but largely ignores the result and assumes that flc_owner
is an nfs4_delegation anyway.  This is wrong.&lt;/p&gt;
&lt;p&gt;With this patch we restore the &amp;#34;!= &amp;amp;nfsd_lease_mng_ops&amp;#34; case to behave
as it did before the change mentioned below.  This is the same as the
current code, but without any reference to a possible delegation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46690</guid>
    </item>
  </channel>
</rss>
