<?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:04:09 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99541</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99541</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix OOB read and cross-share confusion in ksmbd_validate_name_reconnect()&lt;/p&gt;
&lt;p&gt;ksmbd_validate_name_reconnect() indexes
ab_pathname[share-&amp;gt;path_sz + 1] without checking that the path is
longer than share-&amp;gt;path_sz + 1 (d_path() fills the buffer from the
end). A durable fp is not bound to its original share, so a client
can preserve a file from a short-path share and reconnect it on a
long-path share, making strcmp() read past the PATH_MAX buffer -
with a long enough share path this oopses the kernel, and on a
mapped page it also gives a byte-equality oracle on adjacent heap
(the reconnect succeeds exactly when the out-of-bounds string
equals the requested name). A same-share variant with the durable
fp at the share root reads 1 byte past the buffer
(strlen(ab_pathname) == share-&amp;gt;path_sz).&lt;/p&gt;
&lt;p&gt;Check before comparing: the path must be longer than share-&amp;gt;path_sz,
it must start with share-&amp;gt;path, and the next character must be &amp;#39;/&amp;#39;.
The share root itself is accepted only for an empty name.&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: fix OOB read and cross-share confusion in ksmbd_validate_name_reconnect()&lt;/p&gt;
&lt;p&gt;ksmbd_validate_name_reconnect() indexes
ab_pathname[share-&amp;gt;path_sz + 1] without checking that the path is
longer than share-&amp;gt;path_sz + 1 (d_path() fills the buffer from the
end). A durable fp is not bound to its original share, so a client
can preserve a file from a short-path share and reconnect it on a
long-path share, making strcmp() read past the PATH_MAX buffer -
with a long enough share path this oopses the kernel, and on a
mapped page it also gives a byte-equality oracle on adjacent heap
(the reconnect succeeds exactly when the out-of-bounds string
equals the requested name). A same-share variant with the durable
fp at the share root reads 1 byte past the buffer
(strlen(ab_pathname) == share-&amp;gt;path_sz).&lt;/p&gt;
&lt;p&gt;Check before comparing: the path must be longer than share-&amp;gt;path_sz,
it must start with share-&amp;gt;path, and the next character must be &amp;#39;/&amp;#39;.
The share root itself is accepted only for an empty name.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99541</guid>
    </item>
    <item>
      <title>GHSA-wfwm-5fwf-6gcj</title>
      <link>https://db.gcve.eu/vuln/ghsa-wfwm-5fwf-6gcj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix OOB read and cross-share confusion in ksmbd_validate_name_reconnect()&lt;/p&gt;
&lt;p&gt;ksmbd_validate_name_reconnect() indexes
ab_pathname[share-&amp;gt;path_sz + 1] without checking that the path is
longer than share-&amp;gt;path_sz + 1 (d_path() fills the buffer from the
end). A durable fp is not bound to its original share, so a client
can preserve a file from a short-path share and reconnect it on a
long-path share, making strcmp() read past the PATH_MAX buffer -
with a long enough share path this oopses the kernel, and on a
mapped page it also gives a byte-equality oracle on adjacent heap
(the reconnect succeeds exactly when the out-of-bounds string
equals the requested name). A same-share variant with the durable
fp at the share root reads 1 byte past the buffer
(strlen(ab_pathname) == share-&amp;gt;path_sz).&lt;/p&gt;
&lt;p&gt;Check before comparing: the path must be longer than share-&amp;gt;path_sz,
it must start with share-&amp;gt;path, and the next character must be &amp;#39;/&amp;#39;.
The share root itself is accepted only for an empty name.&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: fix OOB read and cross-share confusion in ksmbd_validate_name_reconnect()&lt;/p&gt;
&lt;p&gt;ksmbd_validate_name_reconnect() indexes
ab_pathname[share-&amp;gt;path_sz + 1] without checking that the path is
longer than share-&amp;gt;path_sz + 1 (d_path() fills the buffer from the
end). A durable fp is not bound to its original share, so a client
can preserve a file from a short-path share and reconnect it on a
long-path share, making strcmp() read past the PATH_MAX buffer -
with a long enough share path this oopses the kernel, and on a
mapped page it also gives a byte-equality oracle on adjacent heap
(the reconnect succeeds exactly when the out-of-bounds string
equals the requested name). A same-share variant with the durable
fp at the share root reads 1 byte past the buffer
(strlen(ab_pathname) == share-&amp;gt;path_sz).&lt;/p&gt;
&lt;p&gt;Check before comparing: the path must be longer than share-&amp;gt;path_sz,
it must start with share-&amp;gt;path, and the next character must be &amp;#39;/&amp;#39;.
The share root itself is accepted only for an empty name.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-wfwm-5fwf-6gcj</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>
