https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 02:19:29 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-03245 bdu:2026-03245 https://cve.radiocsirt.org/vuln/bdu:2026-03245 https://cve.radiocsirt.org/vuln/bell-cve-2023-4130 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2023-4130 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0787 certfr-2025-avi-0787 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0787 https://cve.radiocsirt.org/vuln/euvd-2026-353071 EUVD-2026-353071 https://cve.radiocsirt.org/vuln/euvd-2026-353071 https://cve.radiocsirt.org/vuln/fkie_cve-2023-4130 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()</p> <p>There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using -&gt;NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()</p> <p>There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using -&gt;NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-4130 https://cve.radiocsirt.org/vuln/ghsa-3ccm-2cr5-453p <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()</p> <p>There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using -&gt;NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()</p> <p>There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using -&gt;NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.</p> https://cve.radiocsirt.org/vuln/ghsa-3ccm-2cr5-453p https://cve.radiocsirt.org/vuln/gsd-2023-4130 gsd-2023-4130 https://cve.radiocsirt.org/vuln/gsd-2023-4130 https://cve.radiocsirt.org/vuln/suse-su-2025:03272-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:03272-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-4130 <p><strong>Affected:</strong> 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</p> <p>In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using -&gt;NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.</p> <p><strong>Affected:</strong> 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</p> <p>In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using -&gt;NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-4130 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1858 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1858