https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 01:16:53 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46315 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-46315 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0809 certfr-2026-avi-0809 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0809 https://cve.radiocsirt.org/vuln/euvd-2026-327215 EUVD-2026-327215 https://cve.radiocsirt.org/vuln/euvd-2026-327215 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46315 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/waitid: clear waitid info before copying it to userspace</p> <p>IORING_OP_WAITID stores its result fields in struct io_waitid::info and later copies them to userspace siginfo. The prep path initializes the request arguments, but it does not initialize info itself.</p> <p>If the wait operation completes without reporting a child event, the common wait code can return without writing wo_info. In that case io_waitid_finish() still copies iw-&gt;info to userspace, exposing stale bytes from the reused io_kiocb command storage.</p> <p>Clear the result storage during prep so the io_uring path matches the regular waitid syscall, which uses a zero-initialized struct waitid_info.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/waitid: clear waitid info before copying it to userspace</p> <p>IORING_OP_WAITID stores its result fields in struct io_waitid::info and later copies them to userspace siginfo. The prep path initializes the request arguments, but it does not initialize info itself.</p> <p>If the wait operation completes without reporting a child event, the common wait code can return without writing wo_info. In that case io_waitid_finish() still copies iw-&gt;info to userspace, exposing stale bytes from the reused io_kiocb command storage.</p> <p>Clear the result storage during prep so the io_uring path matches the regular waitid syscall, which uses a zero-initialized struct waitid_info.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46315 https://cve.radiocsirt.org/vuln/ghsa-3xr6-r26v-fpqm <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/waitid: clear waitid info before copying it to userspace</p> <p>IORING_OP_WAITID stores its result fields in struct io_waitid::info and later copies them to userspace siginfo. The prep path initializes the request arguments, but it does not initialize info itself.</p> <p>If the wait operation completes without reporting a child event, the common wait code can return without writing wo_info. In that case io_waitid_finish() still copies iw-&gt;info to userspace, exposing stale bytes from the reused io_kiocb command storage.</p> <p>Clear the result storage during prep so the io_uring path matches the regular waitid syscall, which uses a zero-initialized struct waitid_info.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/waitid: clear waitid info before copying it to userspace</p> <p>IORING_OP_WAITID stores its result fields in struct io_waitid::info and later copies them to userspace siginfo. The prep path initializes the request arguments, but it does not initialize info itself.</p> <p>If the wait operation completes without reporting a child event, the common wait code can return without writing wo_info. In that case io_waitid_finish() still copies iw-&gt;info to userspace, exposing stale bytes from the reused io_kiocb command storage.</p> <p>Clear the result storage during prep so the io_uring path matches the regular waitid syscall, which uses a zero-initialized struct waitid_info.</p> https://cve.radiocsirt.org/vuln/ghsa-3xr6-r26v-fpqm https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 <p>kernel-devel-7.0.12-1.1 on GA media</p> <p>kernel-devel-7.0.12-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46315 <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 162 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: clear waitid info before copying it to userspace IORING_OP_WAITID stores its result fields in struct io_waitid::info and later copies them to userspace siginfo. The prep path initializes the request arguments, but it does not initialize info itself. If the wait operation completes without reporting a child event, the common wait code can return without writing wo_info. In that case io_waitid_finish() still copies iw-&gt;info to userspace, exposing stale bytes from the reused io_kiocb command storage. Clear the result storage during prep so the io_uring path matches the regular waitid syscall, which uses a zero-initialized struct waitid_info.</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 162 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: clear waitid info before copying it to userspace IORING_OP_WAITID stores its result fields in struct io_waitid::info and later copies them to userspace siginfo. The prep path initializes the request arguments, but it does not initialize info itself. If the wait operation completes without reporting a child event, the common wait code can return without writing wo_info. In that case io_waitid_finish() still copies iw-&gt;info to userspace, exposing stale bytes from the reused io_kiocb command storage. Clear the result storage during prep so the io_uring path matches the regular waitid syscall, which uses a zero-initialized struct waitid_info.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46315 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1827 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1827