https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 18:10:26 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-12560 bdu:2026-12560 https://cve.radiocsirt.org/vuln/bdu:2026-12560 https://cve.radiocsirt.org/vuln/bell-cve-2026-31554 <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-31554 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0548 certfr-2026-avi-0548 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0548 https://cve.radiocsirt.org/vuln/euvd-2026-347716 EUVD-2026-347716 https://cve.radiocsirt.org/vuln/euvd-2026-347716 https://cve.radiocsirt.org/vuln/fkie_cve-2026-31554 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>futex: Require sys_futex_requeue() to have identical flags</p> <p>Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn&#39;t been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>futex: Require sys_futex_requeue() to have identical flags</p> <p>Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn&#39;t been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-31554 https://cve.radiocsirt.org/vuln/ghsa-fqg3-p6v9-g3wx <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>futex: Require sys_futex_requeue() to have identical flags</p> <p>Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn&#39;t been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>futex: Require sys_futex_requeue() to have identical flags</p> <p>Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn&#39;t been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.</p> https://cve.radiocsirt.org/vuln/ghsa-fqg3-p6v9-g3wx https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1 https://cve.radiocsirt.org/vuln/suse-su-2026:21834-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:21834-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31554 <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 140 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: futex: Require sys_futex_requeue() to have identical flags Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn&#39;t been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.</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 140 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: futex: Require sys_futex_requeue() to have identical flags Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn&#39;t been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31554 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279