<?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 07:27:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89839 — f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89839</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;f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set()&lt;/p&gt;
&lt;p&gt;f2fs_xattr_advise_set() calls inode_owner_or_capable() with &amp;amp;nop_mnt_idmap
before allowing the &amp;#34;system.advise&amp;#34; xattr to be set, instead of the idmap
that the VFS passes to the -&amp;gt;set() handler.&lt;/p&gt;
&lt;p&gt;f2fs supports idmapped mounts, so on such a mount this checks the caller&amp;#39;s
fsuid against the unmapped on-disk owner rather than the mapped owner: the
actual owner can be wrongly denied with -EPERM and an unrelated caller
wrongly allowed.  Pass the handler&amp;#39;s idmap instead.&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;f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set()&lt;/p&gt;
&lt;p&gt;f2fs_xattr_advise_set() calls inode_owner_or_capable() with &amp;amp;nop_mnt_idmap
before allowing the &amp;#34;system.advise&amp;#34; xattr to be set, instead of the idmap
that the VFS passes to the -&amp;gt;set() handler.&lt;/p&gt;
&lt;p&gt;f2fs supports idmapped mounts, so on such a mount this checks the caller&amp;#39;s
fsuid against the unmapped on-disk owner rather than the mapped owner: the
actual owner can be wrongly denied with -EPERM and an unrelated caller
wrongly allowed.  Pass the handler&amp;#39;s idmap instead.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89839</guid>
    </item>
  </channel>
</rss>
