<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 18:29:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64139</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64139</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-64139</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-357819</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-357819</link>
      <description>EUVD-2026-357819</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-357819</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64139</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64139</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix SID memory leak in set_posix_acl_entries_dacl() on overflow&lt;/p&gt;
&lt;p&gt;Commit 299f962c0b02 (&amp;#34;ksmbd: use check_add_overflow() to prevent u16
DACL size overflow&amp;#34;) added check_add_overflow() guards that break out
of the ACE-building loops in set_posix_acl_entries_dacl() when the
accumulated DACL size would wrap past 65535.&lt;/p&gt;
&lt;p&gt;However, each iteration allocates a struct smb_sid via kmalloc_obj()
at the top of the loop and relies on the kfree(sid) call at the end
of the loop body (the &amp;#39;pass_same_sid&amp;#39; label in the first loop, and
the explicit kfree at the tail of the second loop) to release it.
The newly introduced &amp;#39;break&amp;#39; statements bypass those kfree() calls,
leaking the sid buffer every time an overflow is detected.&lt;/p&gt;
&lt;p&gt;A malicious or malformed file with enough POSIX ACL entries to trip
the overflow check will leak one or more struct smb_sid allocations
on every request that touches the file&amp;#39;s DACL, providing a trivial
kernel memory exhaustion vector.&lt;/p&gt;
&lt;p&gt;Free sid before breaking out of the loops to plug the leak.&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 SID memory leak in set_posix_acl_entries_dacl() on overflow&lt;/p&gt;
&lt;p&gt;Commit 299f962c0b02 (&amp;#34;ksmbd: use check_add_overflow() to prevent u16
DACL size overflow&amp;#34;) added check_add_overflow() guards that break out
of the ACE-building loops in set_posix_acl_entries_dacl() when the
accumulated DACL size would wrap past 65535.&lt;/p&gt;
&lt;p&gt;However, each iteration allocates a struct smb_sid via kmalloc_obj()
at the top of the loop and relies on the kfree(sid) call at the end
of the loop body (the &amp;#39;pass_same_sid&amp;#39; label in the first loop, and
the explicit kfree at the tail of the second loop) to release it.
The newly introduced &amp;#39;break&amp;#39; statements bypass those kfree() calls,
leaking the sid buffer every time an overflow is detected.&lt;/p&gt;
&lt;p&gt;A malicious or malformed file with enough POSIX ACL entries to trip
the overflow check will leak one or more struct smb_sid allocations
on every request that touches the file&amp;#39;s DACL, providing a trivial
kernel memory exhaustion vector.&lt;/p&gt;
&lt;p&gt;Free sid before breaking out of the loops to plug the leak.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64139</guid>
    </item>
    <item>
      <title>GHSA-3c28-w5w6-mh56</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3c28-w5w6-mh56</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix SID memory leak in set_posix_acl_entries_dacl() on overflow&lt;/p&gt;
&lt;p&gt;Commit 299f962c0b02 (&amp;#34;ksmbd: use check_add_overflow() to prevent u16
DACL size overflow&amp;#34;) added check_add_overflow() guards that break out
of the ACE-building loops in set_posix_acl_entries_dacl() when the
accumulated DACL size would wrap past 65535.&lt;/p&gt;
&lt;p&gt;However, each iteration allocates a struct smb_sid via kmalloc_obj()
at the top of the loop and relies on the kfree(sid) call at the end
of the loop body (the &amp;#39;pass_same_sid&amp;#39; label in the first loop, and
the explicit kfree at the tail of the second loop) to release it.
The newly introduced &amp;#39;break&amp;#39; statements bypass those kfree() calls,
leaking the sid buffer every time an overflow is detected.&lt;/p&gt;
&lt;p&gt;A malicious or malformed file with enough POSIX ACL entries to trip
the overflow check will leak one or more struct smb_sid allocations
on every request that touches the file&amp;#39;s DACL, providing a trivial
kernel memory exhaustion vector.&lt;/p&gt;
&lt;p&gt;Free sid before breaking out of the loops to plug the leak.&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 SID memory leak in set_posix_acl_entries_dacl() on overflow&lt;/p&gt;
&lt;p&gt;Commit 299f962c0b02 (&amp;#34;ksmbd: use check_add_overflow() to prevent u16
DACL size overflow&amp;#34;) added check_add_overflow() guards that break out
of the ACE-building loops in set_posix_acl_entries_dacl() when the
accumulated DACL size would wrap past 65535.&lt;/p&gt;
&lt;p&gt;However, each iteration allocates a struct smb_sid via kmalloc_obj()
at the top of the loop and relies on the kfree(sid) call at the end
of the loop body (the &amp;#39;pass_same_sid&amp;#39; label in the first loop, and
the explicit kfree at the tail of the second loop) to release it.
The newly introduced &amp;#39;break&amp;#39; statements bypass those kfree() calls,
leaking the sid buffer every time an overflow is detected.&lt;/p&gt;
&lt;p&gt;A malicious or malformed file with enough POSIX ACL entries to trip
the overflow check will leak one or more struct smb_sid allocations
on every request that touches the file&amp;#39;s DACL, providing a trivial
kernel memory exhaustion vector.&lt;/p&gt;
&lt;p&gt;Free sid before breaking out of the loops to plug the leak.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3c28-w5w6-mh56</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64139</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64139</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix SID memory leak in set_posix_acl_entries_dacl() on overflow Commit 299f962c0b02 (&amp;#34;ksmbd: use check_add_overflow() to prevent u16 DACL size overflow&amp;#34;) added check_add_overflow() guards that break out of the ACE-building loops in set_posix_acl_entries_dacl() when the accumulated DACL size would wrap past 65535. However, each iteration allocates a struct smb_sid via kmalloc_obj() at the top of the loop and relies on the kfree(sid) call at the end of the loop body (the &amp;#39;pass_same_sid&amp;#39; label in the first loop, and the explicit kfree at the tail of the second loop) to release it. The newly introduced &amp;#39;break&amp;#39; statements bypass those kfree() calls, leaking the sid buffer every time an overflow is detected. A malicious or malformed file with enough POSIX ACL entries to trip the overflow check will leak one or more struct smb_sid allocations on every request that touches the file&amp;#39;s DACL, providing a trivial kernel memory exhaustion vector. Free sid before breaking out of the loops to plug the leak.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix SID memory leak in set_posix_acl_entries_dacl() on overflow Commit 299f962c0b02 (&amp;#34;ksmbd: use check_add_overflow() to prevent u16 DACL size overflow&amp;#34;) added check_add_overflow() guards that break out of the ACE-building loops in set_posix_acl_entries_dacl() when the accumulated DACL size would wrap past 65535. However, each iteration allocates a struct smb_sid via kmalloc_obj() at the top of the loop and relies on the kfree(sid) call at the end of the loop body (the &amp;#39;pass_same_sid&amp;#39; label in the first loop, and the explicit kfree at the tail of the second loop) to release it. The newly introduced &amp;#39;break&amp;#39; statements bypass those kfree() calls, leaking the sid buffer every time an overflow is detected. A malicious or malformed file with enough POSIX ACL entries to trip the overflow check will leak one or more struct smb_sid allocations on every request that touches the file&amp;#39;s DACL, providing a trivial kernel memory exhaustion vector. Free sid before breaking out of the loops to plug the leak.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64139</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</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 Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&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 Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
