<?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 08:46:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-52906 — 9p: fix access mode flags being ORed instead of replaced</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-52906</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;9p: fix access mode flags being ORed instead of replaced&lt;/p&gt;
&lt;p&gt;Since commit 1f3e4142c0eb (&amp;#34;9p: convert to the new mount API&amp;#34;),
v9fs_apply_options() applies parsed mount flags with |= onto flags
already set by v9fs_session_init(). For 9P2000.L, session_init sets
V9FS_ACCESS_CLIENT as the default, so when the user mounts with
&amp;#34;access=user&amp;#34;, both bits end up set. Access mode checks compare
against exact values, so having both bits set matches neither mode.&lt;/p&gt;
&lt;p&gt;This causes v9fs_fid_lookup() to fall through to the default switch
case, using INVALID_UID (nobody/65534) instead of current_fsuid()
for all fid lookups. Root is then unable to chown or perform other
privileged operations.&lt;/p&gt;
&lt;p&gt;Fix by clearing the access mask before applying the user&amp;#39;s choice.&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;9p: fix access mode flags being ORed instead of replaced&lt;/p&gt;
&lt;p&gt;Since commit 1f3e4142c0eb (&amp;#34;9p: convert to the new mount API&amp;#34;),
v9fs_apply_options() applies parsed mount flags with |= onto flags
already set by v9fs_session_init(). For 9P2000.L, session_init sets
V9FS_ACCESS_CLIENT as the default, so when the user mounts with
&amp;#34;access=user&amp;#34;, both bits end up set. Access mode checks compare
against exact values, so having both bits set matches neither mode.&lt;/p&gt;
&lt;p&gt;This causes v9fs_fid_lookup() to fall through to the default switch
case, using INVALID_UID (nobody/65534) instead of current_fsuid()
for all fid lookups. Root is then unable to chown or perform other
privileged operations.&lt;/p&gt;
&lt;p&gt;Fix by clearing the access mask before applying the user&amp;#39;s choice.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-52906</guid>
    </item>
  </channel>
</rss>
