<?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:27:44 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99542</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99542</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: deny access for an empty DACL instead of granting the request&lt;/p&gt;
&lt;p&gt;smb_check_perm_dacl() returns the access mask it computes to the SMB2
CREATE handler, which uses it as the granted access for the open. For a
security descriptor whose DACL is present but contains no ACEs, the
function is supposed to deny access: an empty (non-NULL) DACL grants no
access to anyone except the object owner&amp;#39;s implicit READ_CONTROL and
WRITE_DAC (MS-DTYP 2.4.5).&lt;/p&gt;
&lt;p&gt;The empty-DACL branch only denies when both&lt;/p&gt;
&lt;p&gt;- the DACL has no trailing bytes (pdacl_size == sizeof(struct smb_acl)),
    and
  - the request contains bits beyond READ_CONTROL / WRITE_DAC.&lt;/p&gt;
&lt;p&gt;In every other case it takes the shared &amp;#34;goto err_out&amp;#34; with rc still 0,
which returns success without modifying *pdaccess, so the caller grants
the full requested access. Three problems follow:&lt;/p&gt;
&lt;p&gt;- The READ_CONTROL / WRITE_DAC carve-out models the owner&amp;#39;s implicit
    rights, but the check runs before is_owner is computed, so those
    rights are handed to *every* caller, not just the owner. For
    READ_CONTROL the SMB2 CREATE path does not fall back to
    inode_permission(), so any user can read the security descriptor of
    an object whose empty DACL is meant to deny them.&lt;/p&gt;
&lt;p&gt;- A request of exactly READ_CONTROL and/or WRITE_DAC is granted to any
    caller. WRITE_DAC lets the handle rewrite the DACL.&lt;/p&gt;
&lt;p&gt;- A DACL that declares zero ACEs but carries trailing bytes
    (pdacl…&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: deny access for an empty DACL instead of granting the request&lt;/p&gt;
&lt;p&gt;smb_check_perm_dacl() returns the access mask it computes to the SMB2
CREATE handler, which uses it as the granted access for the open. For a
security descriptor whose DACL is present but contains no ACEs, the
function is supposed to deny access: an empty (non-NULL) DACL grants no
access to anyone except the object owner&amp;#39;s implicit READ_CONTROL and
WRITE_DAC (MS-DTYP 2.4.5).&lt;/p&gt;
&lt;p&gt;The empty-DACL branch only denies when both&lt;/p&gt;
&lt;p&gt;- the DACL has no trailing bytes (pdacl_size == sizeof(struct smb_acl)),
    and
  - the request contains bits beyond READ_CONTROL / WRITE_DAC.&lt;/p&gt;
&lt;p&gt;In every other case it takes the shared &amp;#34;goto err_out&amp;#34; with rc still 0,
which returns success without modifying *pdaccess, so the caller grants
the full requested access. Three problems follow:&lt;/p&gt;
&lt;p&gt;- The READ_CONTROL / WRITE_DAC carve-out models the owner&amp;#39;s implicit
    rights, but the check runs before is_owner is computed, so those
    rights are handed to *every* caller, not just the owner. For
    READ_CONTROL the SMB2 CREATE path does not fall back to
    inode_permission(), so any user can read the security descriptor of
    an object whose empty DACL is meant to deny them.&lt;/p&gt;
&lt;p&gt;- A request of exactly READ_CONTROL and/or WRITE_DAC is granted to any
    caller. WRITE_DAC lets the handle rewrite the DACL.&lt;/p&gt;
&lt;p&gt;- A DACL that declares zero ACEs but carries trailing bytes
    (pdacl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99542</guid>
    </item>
    <item>
      <title>GHSA-4qh3-gccr-q67m</title>
      <link>https://db.gcve.eu/vuln/ghsa-4qh3-gccr-q67m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: deny access for an empty DACL instead of granting the request&lt;/p&gt;
&lt;p&gt;smb_check_perm_dacl() returns the access mask it computes to the SMB2
CREATE handler, which uses it as the granted access for the open. For a
security descriptor whose DACL is present but contains no ACEs, the
function is supposed to deny access: an empty (non-NULL) DACL grants no
access to anyone except the object owner&amp;#39;s implicit READ_CONTROL and
WRITE_DAC (MS-DTYP 2.4.5).&lt;/p&gt;
&lt;p&gt;The empty-DACL branch only denies when both&lt;/p&gt;
&lt;p&gt;- the DACL has no trailing bytes (pdacl_size == sizeof(struct smb_acl)),
    and
  - the request contains bits beyond READ_CONTROL / WRITE_DAC.&lt;/p&gt;
&lt;p&gt;In every other case it takes the shared &amp;#34;goto err_out&amp;#34; with rc still 0,
which returns success without modifying *pdaccess, so the caller grants
the full requested access. Three problems follow:&lt;/p&gt;
&lt;p&gt;- The READ_CONTROL / WRITE_DAC carve-out models the owner&amp;#39;s implicit
    rights, but the check runs before is_owner is computed, so those
    rights are handed to *every* caller, not just the owner. For
    READ_CONTROL the SMB2 CREATE path does not fall back to
    inode_permission(), so any user can read the security descriptor of
    an object whose empty DACL is meant to deny them.&lt;/p&gt;
&lt;p&gt;- A request of exactly READ_CONTROL and/or WRITE_DAC is granted to any
    caller. WRITE_DAC lets the handle rewrite the DACL.&lt;/p&gt;
&lt;p&gt;- A DACL that declares zero ACEs but carries trailing bytes
    (pdacl…&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: deny access for an empty DACL instead of granting the request&lt;/p&gt;
&lt;p&gt;smb_check_perm_dacl() returns the access mask it computes to the SMB2
CREATE handler, which uses it as the granted access for the open. For a
security descriptor whose DACL is present but contains no ACEs, the
function is supposed to deny access: an empty (non-NULL) DACL grants no
access to anyone except the object owner&amp;#39;s implicit READ_CONTROL and
WRITE_DAC (MS-DTYP 2.4.5).&lt;/p&gt;
&lt;p&gt;The empty-DACL branch only denies when both&lt;/p&gt;
&lt;p&gt;- the DACL has no trailing bytes (pdacl_size == sizeof(struct smb_acl)),
    and
  - the request contains bits beyond READ_CONTROL / WRITE_DAC.&lt;/p&gt;
&lt;p&gt;In every other case it takes the shared &amp;#34;goto err_out&amp;#34; with rc still 0,
which returns success without modifying *pdaccess, so the caller grants
the full requested access. Three problems follow:&lt;/p&gt;
&lt;p&gt;- The READ_CONTROL / WRITE_DAC carve-out models the owner&amp;#39;s implicit
    rights, but the check runs before is_owner is computed, so those
    rights are handed to *every* caller, not just the owner. For
    READ_CONTROL the SMB2 CREATE path does not fall back to
    inode_permission(), so any user can read the security descriptor of
    an object whose empty DACL is meant to deny them.&lt;/p&gt;
&lt;p&gt;- A request of exactly READ_CONTROL and/or WRITE_DAC is granted to any
    caller. WRITE_DAC lets the handle rewrite the DACL.&lt;/p&gt;
&lt;p&gt;- A DACL that declares zero ACEs but carries trailing bytes
    (pdacl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-4qh3-gccr-q67m</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>
