<?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 22:50:54 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46139</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-46139</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-46139</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-327142</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327142</link>
      <description>EUVD-2026-327142</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327142</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46139</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46139</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: use kzalloc to zero-initialize security descriptor buffer&lt;/p&gt;
&lt;p&gt;Commit 62e7dd0a39c2d (&amp;#34;smb: common: change the data type of num_aces
to le16&amp;#34;) split struct smb_acl&amp;#39;s __le32 num_aces field into __le16
num_aces and __le16 reserved. The reserved field corresponds to Sbz2
in the MS-DTYP ACL wire format, which must be zero [1].&lt;/p&gt;
&lt;p&gt;When building an ACL descriptor in build_sec_desc(), we are using a
kmalloc()&amp;#39;ed descriptor buffer and writing the fields explicitly using
le16() writes now. This never writes to the 2 byte reserved field,
leaving it as uninitialized heap data.&lt;/p&gt;
&lt;p&gt;When the reserved field happens to contain non-zero slab garbage,
Samba rejects the security descriptor with &amp;#34;ndr_pull_security_descriptor
failed: Range Error&amp;#34;, causing chmod to fail with EINVAL.&lt;/p&gt;
&lt;p&gt;Change kmalloc() to kzalloc() to ensure the entire buffer is
zero-initialized.&lt;/p&gt;
&lt;p&gt;[1] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/20233ed8-a6c6-4097-aafa-dd545ed24428&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;smb: client: use kzalloc to zero-initialize security descriptor buffer&lt;/p&gt;
&lt;p&gt;Commit 62e7dd0a39c2d (&amp;#34;smb: common: change the data type of num_aces
to le16&amp;#34;) split struct smb_acl&amp;#39;s __le32 num_aces field into __le16
num_aces and __le16 reserved. The reserved field corresponds to Sbz2
in the MS-DTYP ACL wire format, which must be zero [1].&lt;/p&gt;
&lt;p&gt;When building an ACL descriptor in build_sec_desc(), we are using a
kmalloc()&amp;#39;ed descriptor buffer and writing the fields explicitly using
le16() writes now. This never writes to the 2 byte reserved field,
leaving it as uninitialized heap data.&lt;/p&gt;
&lt;p&gt;When the reserved field happens to contain non-zero slab garbage,
Samba rejects the security descriptor with &amp;#34;ndr_pull_security_descriptor
failed: Range Error&amp;#34;, causing chmod to fail with EINVAL.&lt;/p&gt;
&lt;p&gt;Change kmalloc() to kzalloc() to ensure the entire buffer is
zero-initialized.&lt;/p&gt;
&lt;p&gt;[1] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/20233ed8-a6c6-4097-aafa-dd545ed24428&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46139</guid>
    </item>
    <item>
      <title>GHSA-v8jf-78w3-v9hm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v8jf-78w3-v9hm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: use kzalloc to zero-initialize security descriptor buffer&lt;/p&gt;
&lt;p&gt;Commit 62e7dd0a39c2d (&amp;#34;smb: common: change the data type of num_aces
to le16&amp;#34;) split struct smb_acl&amp;#39;s __le32 num_aces field into __le16
num_aces and __le16 reserved. The reserved field corresponds to Sbz2
in the MS-DTYP ACL wire format, which must be zero [1].&lt;/p&gt;
&lt;p&gt;When building an ACL descriptor in build_sec_desc(), we are using a
kmalloc()&amp;#39;ed descriptor buffer and writing the fields explicitly using
le16() writes now. This never writes to the 2 byte reserved field,
leaving it as uninitialized heap data.&lt;/p&gt;
&lt;p&gt;When the reserved field happens to contain non-zero slab garbage,
Samba rejects the security descriptor with &amp;#34;ndr_pull_security_descriptor
failed: Range Error&amp;#34;, causing chmod to fail with EINVAL.&lt;/p&gt;
&lt;p&gt;Change kmalloc() to kzalloc() to ensure the entire buffer is
zero-initialized.&lt;/p&gt;
&lt;p&gt;[1] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/20233ed8-a6c6-4097-aafa-dd545ed24428&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;smb: client: use kzalloc to zero-initialize security descriptor buffer&lt;/p&gt;
&lt;p&gt;Commit 62e7dd0a39c2d (&amp;#34;smb: common: change the data type of num_aces
to le16&amp;#34;) split struct smb_acl&amp;#39;s __le32 num_aces field into __le16
num_aces and __le16 reserved. The reserved field corresponds to Sbz2
in the MS-DTYP ACL wire format, which must be zero [1].&lt;/p&gt;
&lt;p&gt;When building an ACL descriptor in build_sec_desc(), we are using a
kmalloc()&amp;#39;ed descriptor buffer and writing the fields explicitly using
le16() writes now. This never writes to the 2 byte reserved field,
leaving it as uninitialized heap data.&lt;/p&gt;
&lt;p&gt;When the reserved field happens to contain non-zero slab garbage,
Samba rejects the security descriptor with &amp;#34;ndr_pull_security_descriptor
failed: Range Error&amp;#34;, causing chmod to fail with EINVAL.&lt;/p&gt;
&lt;p&gt;Change kmalloc() to kzalloc() to ensure the entire buffer is
zero-initialized.&lt;/p&gt;
&lt;p&gt;[1] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/20233ed8-a6c6-4097-aafa-dd545ed24428&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v8jf-78w3-v9hm</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10954-1 — kernel-devel-7.0.11-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</link>
      <description>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46139</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46139</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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: use kzalloc to zero-initialize security descriptor buffer Commit 62e7dd0a39c2d (&amp;#34;smb: common: change the data type of num_aces to le16&amp;#34;) split struct smb_acl&amp;#39;s __le32 num_aces field into __le16 num_aces and __le16 reserved. The reserved field corresponds to Sbz2 in the MS-DTYP ACL wire format, which must be zero [1]. When building an ACL descriptor in build_sec_desc(), we are using a kmalloc()&amp;#39;ed descriptor buffer and writing the fields explicitly using le16() writes now. This never writes to the 2 byte reserved field, leaving it as uninitialized heap data. When the reserved field happens to contain non-zero slab garbage, Samba rejects the security descriptor with &amp;#34;ndr_pull_security_descriptor failed: Range Error&amp;#34;, causing chmod to fail with EINVAL. Change kmalloc() to kzalloc() to ensure the entire buffer is zero-initialized. [1] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/20233ed8-a6c6-4097-aafa-dd545ed24428&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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: use kzalloc to zero-initialize security descriptor buffer Commit 62e7dd0a39c2d (&amp;#34;smb: common: change the data type of num_aces to le16&amp;#34;) split struct smb_acl&amp;#39;s __le32 num_aces field into __le16 num_aces and __le16 reserved. The reserved field corresponds to Sbz2 in the MS-DTYP ACL wire format, which must be zero [1]. When building an ACL descriptor in build_sec_desc(), we are using a kmalloc()&amp;#39;ed descriptor buffer and writing the fields explicitly using le16() writes now. This never writes to the 2 byte reserved field, leaving it as uninitialized heap data. When the reserved field happens to contain non-zero slab garbage, Samba rejects the security descriptor with &amp;#34;ndr_pull_security_descriptor failed: Range Error&amp;#34;, causing chmod to fail with EINVAL. Change kmalloc() to kzalloc() to ensure the entire buffer is zero-initialized. [1] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/20233ed8-a6c6-4097-aafa-dd545ed24428&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46139</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</guid>
    </item>
  </channel>
</rss>
