<?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 20:52:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-52944 — ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-52944</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;ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE&lt;/p&gt;
&lt;p&gt;FSCTL_SET_SPARSE in fsctl_set_sparse() modifies the file&amp;#39;s sparse
attribute and saves it through xattr without any permission checks.&lt;/p&gt;
&lt;p&gt;This exposes two issues:&lt;/p&gt;
&lt;p&gt;1) A client on a read-only share can change the sparse attribute
   on files it opened, even though the share is read-only.
   Other FSCTL write operations already check
   test_tree_conn_flag(work-&amp;gt;tcon, KSMBD_TREE_CONN_FLAG_WRITABLE),
   but FSCTL_SET_SPARSE does not.&lt;/p&gt;
&lt;p&gt;2) Even on writable shares, clients without FILE_WRITE_DATA or
   FILE_WRITE_ATTRIBUTES access should not modify the sparse
   attribute. Similar handle-level checks exist in other functions
   but are missing here.&lt;/p&gt;
&lt;p&gt;Add both share-level writable check and per-handle access check.
Use goto out on error to avoid leaking file references.&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;ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE&lt;/p&gt;
&lt;p&gt;FSCTL_SET_SPARSE in fsctl_set_sparse() modifies the file&amp;#39;s sparse
attribute and saves it through xattr without any permission checks.&lt;/p&gt;
&lt;p&gt;This exposes two issues:&lt;/p&gt;
&lt;p&gt;1) A client on a read-only share can change the sparse attribute
   on files it opened, even though the share is read-only.
   Other FSCTL write operations already check
   test_tree_conn_flag(work-&amp;gt;tcon, KSMBD_TREE_CONN_FLAG_WRITABLE),
   but FSCTL_SET_SPARSE does not.&lt;/p&gt;
&lt;p&gt;2) Even on writable shares, clients without FILE_WRITE_DATA or
   FILE_WRITE_ATTRIBUTES access should not modify the sparse
   attribute. Similar handle-level checks exist in other functions
   but are missing here.&lt;/p&gt;
&lt;p&gt;Add both share-level writable check and per-handle access check.
Use goto out on error to avoid leaking file references.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-52944</guid>
    </item>
  </channel>
</rss>
