<?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>Fri, 20 Nov 2026 21:30:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99562</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99562</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: reject FSCTL_SET_ZERO_DATA on a directory handle&lt;/p&gt;
&lt;p&gt;An authenticated client with a writable tree connection can open a
directory with FILE_WRITE_DATA and send FSCTL_SET_ZERO_DATA on that
handle. The handler only checks fp-&amp;gt;daccess &amp;amp; FILE_WRITE_DATA_LE, but on
a directory FILE_WRITE_DATA is the legitimate add-file right, so the
check passes. ksmbd_vfs_zero_data() then calls kernel_write() on the
directory file, which has no FMODE_WRITE, and __kernel_write_iter()
hits WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_WRITE)), panicking a
panic_on_warn kernel.&lt;/p&gt;
&lt;p&gt;Before commit 25e414db7033 (&amp;#34;ksmbd: report holes in allocated range
queries&amp;#34;) the dense-file path used vfs_fallocate(), which rejects
directories with -EISDIR. The kernel_write() loop that replaced it has
no such check. Reject a directory handle in ksmbd_vfs_zero_data() before
writing, as ksmbd_vfs_write() already does for SMB2_WRITE.&lt;/p&gt;
&lt;p&gt;WARNING: fs/read_write.c:608 at __kernel_write_iter+0x74b/0x8c0
  Workqueue: ksmbd-io handle_ksmbd_work
  Call Trace:
   kernel_write+0x1ef/0x4d0
   ksmbd_vfs_zero_data+0x413/0x590
   smb2_ioctl+0x21fa/0x66a0
   handle_ksmbd_work+0x61b/0x1ff0&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: reject FSCTL_SET_ZERO_DATA on a directory handle&lt;/p&gt;
&lt;p&gt;An authenticated client with a writable tree connection can open a
directory with FILE_WRITE_DATA and send FSCTL_SET_ZERO_DATA on that
handle. The handler only checks fp-&amp;gt;daccess &amp;amp; FILE_WRITE_DATA_LE, but on
a directory FILE_WRITE_DATA is the legitimate add-file right, so the
check passes. ksmbd_vfs_zero_data() then calls kernel_write() on the
directory file, which has no FMODE_WRITE, and __kernel_write_iter()
hits WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_WRITE)), panicking a
panic_on_warn kernel.&lt;/p&gt;
&lt;p&gt;Before commit 25e414db7033 (&amp;#34;ksmbd: report holes in allocated range
queries&amp;#34;) the dense-file path used vfs_fallocate(), which rejects
directories with -EISDIR. The kernel_write() loop that replaced it has
no such check. Reject a directory handle in ksmbd_vfs_zero_data() before
writing, as ksmbd_vfs_write() already does for SMB2_WRITE.&lt;/p&gt;
&lt;p&gt;WARNING: fs/read_write.c:608 at __kernel_write_iter+0x74b/0x8c0
  Workqueue: ksmbd-io handle_ksmbd_work
  Call Trace:
   kernel_write+0x1ef/0x4d0
   ksmbd_vfs_zero_data+0x413/0x590
   smb2_ioctl+0x21fa/0x66a0
   handle_ksmbd_work+0x61b/0x1ff0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99562</guid>
    </item>
    <item>
      <title>GHSA-2hff-3hr6-gxx5</title>
      <link>https://db.gcve.eu/vuln/ghsa-2hff-3hr6-gxx5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: reject FSCTL_SET_ZERO_DATA on a directory handle&lt;/p&gt;
&lt;p&gt;An authenticated client with a writable tree connection can open a
directory with FILE_WRITE_DATA and send FSCTL_SET_ZERO_DATA on that
handle. The handler only checks fp-&amp;gt;daccess &amp;amp; FILE_WRITE_DATA_LE, but on
a directory FILE_WRITE_DATA is the legitimate add-file right, so the
check passes. ksmbd_vfs_zero_data() then calls kernel_write() on the
directory file, which has no FMODE_WRITE, and __kernel_write_iter()
hits WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_WRITE)), panicking a
panic_on_warn kernel.&lt;/p&gt;
&lt;p&gt;Before commit 25e414db7033 (&amp;#34;ksmbd: report holes in allocated range
queries&amp;#34;) the dense-file path used vfs_fallocate(), which rejects
directories with -EISDIR. The kernel_write() loop that replaced it has
no such check. Reject a directory handle in ksmbd_vfs_zero_data() before
writing, as ksmbd_vfs_write() already does for SMB2_WRITE.&lt;/p&gt;
&lt;p&gt;WARNING: fs/read_write.c:608 at __kernel_write_iter+0x74b/0x8c0
  Workqueue: ksmbd-io handle_ksmbd_work
  Call Trace:
   kernel_write+0x1ef/0x4d0
   ksmbd_vfs_zero_data+0x413/0x590
   smb2_ioctl+0x21fa/0x66a0
   handle_ksmbd_work+0x61b/0x1ff0&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: reject FSCTL_SET_ZERO_DATA on a directory handle&lt;/p&gt;
&lt;p&gt;An authenticated client with a writable tree connection can open a
directory with FILE_WRITE_DATA and send FSCTL_SET_ZERO_DATA on that
handle. The handler only checks fp-&amp;gt;daccess &amp;amp; FILE_WRITE_DATA_LE, but on
a directory FILE_WRITE_DATA is the legitimate add-file right, so the
check passes. ksmbd_vfs_zero_data() then calls kernel_write() on the
directory file, which has no FMODE_WRITE, and __kernel_write_iter()
hits WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_WRITE)), panicking a
panic_on_warn kernel.&lt;/p&gt;
&lt;p&gt;Before commit 25e414db7033 (&amp;#34;ksmbd: report holes in allocated range
queries&amp;#34;) the dense-file path used vfs_fallocate(), which rejects
directories with -EISDIR. The kernel_write() loop that replaced it has
no such check. Reject a directory handle in ksmbd_vfs_zero_data() before
writing, as ksmbd_vfs_write() already does for SMB2_WRITE.&lt;/p&gt;
&lt;p&gt;WARNING: fs/read_write.c:608 at __kernel_write_iter+0x74b/0x8c0
  Workqueue: ksmbd-io handle_ksmbd_work
  Call Trace:
   kernel_write+0x1ef/0x4d0
   ksmbd_vfs_zero_data+0x413/0x590
   smb2_ioctl+0x21fa/0x66a0
   handle_ksmbd_work+0x61b/0x1ff0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2hff-3hr6-gxx5</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
