https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:25:10 +0000 https://cve.radiocsirt.org/vuln/bdu:2020-00235 bdu:2020-00235 https://cve.radiocsirt.org/vuln/bdu:2020-00235 https://cve.radiocsirt.org/vuln/bell-cve-2019-15239 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2019-15239 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-32355 cnvd-2019-32355 https://cve.radiocsirt.org/vuln/cnvd-2019-32355 https://cve.radiocsirt.org/vuln/euvd-2026-57010 EUVD-2026-57010 https://cve.radiocsirt.org/vuln/euvd-2026-57010 https://cve.radiocsirt.org/vuln/fkie_cve-2019-15239 <p>In the Linux kernel, a certain net/ipv4/tcp_output.c change, which was properly incorporated into 4.16.12, was incorrectly backported to the earlier longterm kernels, introducing a new vulnerability that was potentially more severe than the issue that was intended to be fixed by backporting. Specifically, by adding to a write queue between disconnection and re-connection, a local attacker can trigger multiple use-after-free conditions. This can result in a kernel crash, or potentially in privilege escalation. NOTE: this affects (for example) Linux distributions that use 4.9.x longterm kernels before 4.9.190 or 4.14.x longterm kernels before 4.14.139.</p> <p>In the Linux kernel, a certain net/ipv4/tcp_output.c change, which was properly incorporated into 4.16.12, was incorrectly backported to the earlier longterm kernels, introducing a new vulnerability that was potentially more severe than the issue that was intended to be fixed by backporting. Specifically, by adding to a write queue between disconnection and re-connection, a local attacker can trigger multiple use-after-free conditions. This can result in a kernel crash, or potentially in privilege escalation. NOTE: this affects (for example) Linux distributions that use 4.9.x longterm kernels before 4.9.190 or 4.14.x longterm kernels before 4.14.139.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-15239 https://cve.radiocsirt.org/vuln/ghsa-7j8w-38v5-7qqp <p>In the Linux kernel, a certain net/ipv4/tcp_output.c change, which was properly incorporated into 4.16.12, was incorrectly backported to the earlier longterm kernels, introducing a new vulnerability that was potentially more severe than the issue that was intended to be fixed by backporting. Specifically, by adding to a write queue between disconnection and re-connection, a local attacker can trigger multiple use-after-free conditions. This can result in a kernel crash, or potentially in privilege escalation. NOTE: this affects (for example) Linux distributions that use 4.9.x longterm kernels before 4.9.190 or 4.14.x longterm kernels before 4.14.139.</p> <p>In the Linux kernel, a certain net/ipv4/tcp_output.c change, which was properly incorporated into 4.16.12, was incorrectly backported to the earlier longterm kernels, introducing a new vulnerability that was potentially more severe than the issue that was intended to be fixed by backporting. Specifically, by adding to a write queue between disconnection and re-connection, a local attacker can trigger multiple use-after-free conditions. This can result in a kernel crash, or potentially in privilege escalation. NOTE: this affects (for example) Linux distributions that use 4.9.x longterm kernels before 4.9.190 or 4.14.x longterm kernels before 4.14.139.</p> https://cve.radiocsirt.org/vuln/ghsa-7j8w-38v5-7qqp https://cve.radiocsirt.org/vuln/gsd-2019-15239 gsd-2019-15239 https://cve.radiocsirt.org/vuln/gsd-2019-15239 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/rhsa-2019:3978 <p>Kernel: KVM: OOB memory access via mmio ring buffer kernel: local attacker can trigger multiple use-after-free conditions results in privilege escalation</p> <p>Kernel: KVM: OOB memory access via mmio ring buffer kernel: local attacker can trigger multiple use-after-free conditions results in privilege escalation</p> https://cve.radiocsirt.org/vuln/rhsa-2019:3978 https://cve.radiocsirt.org/vuln/suse-su-2019:2412-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:2412-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-15239 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:16.04:LTS: linux, Ubuntu:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-kvm, Ubuntu:16.04:LTS: linux-raspi2, Ubuntu:16.04:LTS: linux-snapdragon, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:20.04:LTS: linux-azure-fde, Ubuntu:20.04:LTS: linux-gke and 6 more</p> <p>In the Linux kernel, a certain net/ipv4/tcp_output.c change, which was properly incorporated into 4.16.12, was incorrectly backported to the earlier longterm kernels, introducing a new vulnerability that was potentially more severe than the issue that was intended to be fixed by backporting. Specifically, by adding to a write queue between disconnection and re-connection, a local attacker can trigger multiple use-after-free conditions. This can result in a kernel crash, or potentially in privilege escalation. NOTE: this affects (for example) Linux distributions that use 4.9.x longterm kernels before 4.9.190 or 4.14.x longterm kernels before 4.14.139.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:16.04:LTS: linux, Ubuntu:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-kvm, Ubuntu:16.04:LTS: linux-raspi2, Ubuntu:16.04:LTS: linux-snapdragon, Ubuntu:Pro:FIPS:16.04:LTS: linux-fips, Ubuntu:20.04:LTS: linux-azure-fde, Ubuntu:20.04:LTS: linux-gke and 6 more</p> <p>In the Linux kernel, a certain net/ipv4/tcp_output.c change, which was properly incorporated into 4.16.12, was incorrectly backported to the earlier longterm kernels, introducing a new vulnerability that was potentially more severe than the issue that was intended to be fixed by backporting. Specifically, by adding to a write queue between disconnection and re-connection, a local attacker can trigger multiple use-after-free conditions. This can result in a kernel crash, or potentially in privilege escalation. NOTE: this affects (for example) Linux distributions that use 4.9.x longterm kernels before 4.9.190 or 4.14.x longterm kernels before 4.14.139.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-15239