<?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://db.gcve.eu</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>Sat, 07 Nov 2026 04:38:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99131 — xfs: fix capability check in xfs</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99131</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;xfs: fix capability check in xfs&lt;/p&gt;
&lt;p&gt;An user reported a bug where he managed to evade group&amp;#39;s quota
by changing a file&amp;#39;s gid to a different group id the same user
belonged to, even though quotas were enforced on both gids and the
file&amp;#39;s size was big enough to exceed the quota&amp;#39;s hardlimit.&lt;/p&gt;
&lt;p&gt;Commit eba0549bc7d1 replaced a capable() call by a
has_capability_noaudit() to prevent unnecessary selinux audit messages.
Turns out that both calls have slightly different semantics even though
their documentation seems similar. Where in a nutshell:&lt;/p&gt;
&lt;p&gt;capable() - Tests the task&amp;#39;s effective credentials
has_ns_capability_noaudit() - Tests the task&amp;#39;s real credentials&lt;/p&gt;
&lt;p&gt;This most of the time has no practical difference but in some cases like
changing attrs (specifically group id in this case) through a NFS client
this will allow the quota code to use XFS_QMOPT_FORCE_RES, effectively
bypassing quota accounting checks.&lt;/p&gt;
&lt;p&gt;Using instead ns_capable_noaudit() should fix this issue and prevent
selinux audit messages.&lt;/p&gt;
&lt;p&gt;This also fix the remaining calls to has_capability_noaudit()&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;xfs: fix capability check in xfs&lt;/p&gt;
&lt;p&gt;An user reported a bug where he managed to evade group&amp;#39;s quota
by changing a file&amp;#39;s gid to a different group id the same user
belonged to, even though quotas were enforced on both gids and the
file&amp;#39;s size was big enough to exceed the quota&amp;#39;s hardlimit.&lt;/p&gt;
&lt;p&gt;Commit eba0549bc7d1 replaced a capable() call by a
has_capability_noaudit() to prevent unnecessary selinux audit messages.
Turns out that both calls have slightly different semantics even though
their documentation seems similar. Where in a nutshell:&lt;/p&gt;
&lt;p&gt;capable() - Tests the task&amp;#39;s effective credentials
has_ns_capability_noaudit() - Tests the task&amp;#39;s real credentials&lt;/p&gt;
&lt;p&gt;This most of the time has no practical difference but in some cases like
changing attrs (specifically group id in this case) through a NFS client
this will allow the quota code to use XFS_QMOPT_FORCE_RES, effectively
bypassing quota accounting checks.&lt;/p&gt;
&lt;p&gt;Using instead ns_capable_noaudit() should fix this issue and prevent
selinux audit messages.&lt;/p&gt;
&lt;p&gt;This also fix the remaining calls to has_capability_noaudit()&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99131</guid>
    </item>
  </channel>
</rss>
