https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 04:43:26 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-01388 bdu:2026-01388 https://cve.radiocsirt.org/vuln/bdu:2026-01388 https://cve.radiocsirt.org/vuln/bell-cve-2025-37880 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-37880 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0559 certfr-2025-avi-0559 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0559 https://cve.radiocsirt.org/vuln/euvd-2026-314298 EUVD-2026-314298 https://cve.radiocsirt.org/vuln/euvd-2026-314298 https://cve.radiocsirt.org/vuln/fkie_cve-2025-37880 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>um: work around sched_yield not yielding in time-travel mode</p> <p>sched_yield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).</p> <p>Work around it by accounting time to the process whenever it executes a sched_yield syscall.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>um: work around sched_yield not yielding in time-travel mode</p> <p>sched_yield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).</p> <p>Work around it by accounting time to the process whenever it executes a sched_yield syscall.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-37880 https://cve.radiocsirt.org/vuln/ghsa-v3qr-5fr6-xpwv <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>um: work around sched_yield not yielding in time-travel mode</p> <p>sched_yield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).</p> <p>Work around it by accounting time to the process whenever it executes a sched_yield syscall.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>um: work around sched_yield not yielding in time-travel mode</p> <p>sched_yield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).</p> <p>Work around it by accounting time to the process whenever it executes a sched_yield syscall.</p> https://cve.radiocsirt.org/vuln/ghsa-v3qr-5fr6-xpwv https://cve.radiocsirt.org/vuln/msrc_cve-2025-37880 msrc_CVE-2025-37880 https://cve.radiocsirt.org/vuln/msrc_cve-2025-37880 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37880 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 210 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: um: work around sched_yield not yielding in time-travel mode sched_yield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS). Work around it by accounting time to the process whenever it executes a sched_yield syscall.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 210 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: um: work around sched_yield not yielding in time-travel mode sched_yield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS). Work around it by accounting time to the process whenever it executes a sched_yield syscall.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37880 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0991 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere, nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere, nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0991