https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 17:38:43 +0000 https://cve.radiocsirt.org/vuln/bdu:2020-00236 bdu:2020-00236 https://cve.radiocsirt.org/vuln/bdu:2020-00236 https://cve.radiocsirt.org/vuln/certfr-2019-avi-455 certfr-2019-avi-455 https://cve.radiocsirt.org/vuln/certfr-2019-avi-455 https://cve.radiocsirt.org/vuln/cnvd-2019-35772 cnvd-2019-35772 https://cve.radiocsirt.org/vuln/cnvd-2019-35772 https://cve.radiocsirt.org/vuln/euvd-2026-57438 EUVD-2026-57438 https://cve.radiocsirt.org/vuln/euvd-2026-57438 https://cve.radiocsirt.org/vuln/fkie_cve-2019-15902 <p>A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream &#34;x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()&#34; commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped.</p> <p>A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream &#34;x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()&#34; commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-15902 https://cve.radiocsirt.org/vuln/ghsa-vww9-mp9g-8qvc <p>A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream &#34;x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()&#34; commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped.</p> <p>A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream &#34;x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()&#34; commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped.</p> https://cve.radiocsirt.org/vuln/ghsa-vww9-mp9g-8qvc https://cve.radiocsirt.org/vuln/gsd-2019-15902 gsd-2019-15902 https://cve.radiocsirt.org/vuln/gsd-2019-15902 https://cve.radiocsirt.org/vuln/opensuse-su-2019:2173-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2019:2173-1 https://cve.radiocsirt.org/vuln/suse-su-2019:14218-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2019:14218-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-15902 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:16.04:LTS: linux, Ubuntu:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-aws-hwe, Ubuntu:16.04:LTS: linux-azure, Ubuntu:16.04:LTS: linux-gcp, Ubuntu:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-kvm and 24 more</p> <p>A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream &#34;x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()&#34; commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:16.04:LTS: linux, Ubuntu:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-aws-hwe, Ubuntu:16.04:LTS: linux-azure, Ubuntu:16.04:LTS: linux-gcp, Ubuntu:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-kvm and 24 more</p> <p>A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream &#34;x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()&#34; commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-15902