<?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 17:56:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90263 — btrfs: check if root is readonly when setting posix acl</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90263</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;btrfs: check if root is readonly when setting posix acl&lt;/p&gt;
&lt;p&gt;For a filesystem which has btrfs read-only property set to true, all
write operations including acl and xattr should be denied. However, acl
can still be set even if btrfs ro property is true.&lt;/p&gt;
&lt;p&gt;This happens because no function on the set_acl code path checks the root
is readonly or not. It was checked in btrfs_setxattr_trans() but got
removed in commit 353c2ea735e4 (&amp;#34;btrfs: remove redundant readonly root
check in btrfs_setxattr_trans&amp;#34;)&lt;/p&gt;
&lt;p&gt;That commit didn&amp;#39;t check if all the callers properly check the root&amp;#39;s
read-only flag. A previous fix is commit b51111271b03 (&amp;#34;btrfs: check if
root is readonly while setting security xattr&amp;#34;).&lt;/p&gt;
&lt;p&gt;Always check if the root is read-only before performing the set acl
operation.&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;btrfs: check if root is readonly when setting posix acl&lt;/p&gt;
&lt;p&gt;For a filesystem which has btrfs read-only property set to true, all
write operations including acl and xattr should be denied. However, acl
can still be set even if btrfs ro property is true.&lt;/p&gt;
&lt;p&gt;This happens because no function on the set_acl code path checks the root
is readonly or not. It was checked in btrfs_setxattr_trans() but got
removed in commit 353c2ea735e4 (&amp;#34;btrfs: remove redundant readonly root
check in btrfs_setxattr_trans&amp;#34;)&lt;/p&gt;
&lt;p&gt;That commit didn&amp;#39;t check if all the callers properly check the root&amp;#39;s
read-only flag. A previous fix is commit b51111271b03 (&amp;#34;btrfs: check if
root is readonly while setting security xattr&amp;#34;).&lt;/p&gt;
&lt;p&gt;Always check if the root is read-only before performing the set acl
operation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90263</guid>
    </item>
  </channel>
</rss>
