https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:10:47 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252 certfr-2025-avi-0252 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252 https://cve.radiocsirt.org/vuln/euvd-2026-320317 EUVD-2026-320317 https://cve.radiocsirt.org/vuln/euvd-2026-320317 https://cve.radiocsirt.org/vuln/fkie_cve-2022-49653 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: piix4: Fix a memory leak in the EFCH MMIO support</p> <p>The recently added support for EFCH MMIO regions introduced a memory leak in that code path. The leak is caused by the fact that release_resource() merely removes the resource from the tree but does not free its memory. We need to call release_mem_region() instead, which does free the memory. As a nice side effect, this brings back some symmetry between the legacy and MMIO paths.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: piix4: Fix a memory leak in the EFCH MMIO support</p> <p>The recently added support for EFCH MMIO regions introduced a memory leak in that code path. The leak is caused by the fact that release_resource() merely removes the resource from the tree but does not free its memory. We need to call release_mem_region() instead, which does free the memory. As a nice side effect, this brings back some symmetry between the legacy and MMIO paths.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-49653 https://cve.radiocsirt.org/vuln/ghsa-6h97-83v8-3wf3 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: piix4: Fix a memory leak in the EFCH MMIO support</p> <p>The recently added support for EFCH MMIO regions introduced a memory leak in that code path. The leak is caused by the fact that release_resource() merely removes the resource from the tree but does not free its memory. We need to call release_mem_region() instead, which does free the memory. As a nice side effect, this brings back some symmetry between the legacy and MMIO paths.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>i2c: piix4: Fix a memory leak in the EFCH MMIO support</p> <p>The recently added support for EFCH MMIO regions introduced a memory leak in that code path. The leak is caused by the fact that release_resource() merely removes the resource from the tree but does not free its memory. We need to call release_mem_region() instead, which does free the memory. As a nice side effect, this brings back some symmetry between the legacy and MMIO paths.</p> https://cve.radiocsirt.org/vuln/ghsa-6h97-83v8-3wf3 https://cve.radiocsirt.org/vuln/rhsa-2023:2951 <p>hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: when setting font with malicious data by ioctl PIO_FONT, kernel will write memory out of bounds kernel: mm/slub: actually fix freelist pointer vs redzoning kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: possible race condition in drivers/tty/tty_buffers.c kernel: use-after-free in ath9k_htc_probe_device() could cause an escalation of privileges kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: media: em28xx: initialize refcount before kref_get kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: use-after-free caused by l2cap_reassemble_sdu() in net/bluetooth/l2cap_core.c kernel: data races around icsk-&gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink reload in devlink_param_get kernel: USB-accessible buffer overflow in brcmfmac kernel: Double-free in split_…</p> <p>hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: when setting font with malicious data by ioctl PIO_FONT, kernel will write memory out of bounds kernel: mm/slub: actually fix freelist pointer vs redzoning kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: possible race condition in drivers/tty/tty_buffers.c kernel: use-after-free in ath9k_htc_probe_device() could cause an escalation of privileges kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: media: em28xx: initialize refcount before kref_get kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: use-after-free caused by l2cap_reassemble_sdu() in net/bluetooth/l2cap_core.c kernel: data races around icsk-&gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink reload in devlink_param_get kernel: USB-accessible buffer overflow in brcmfmac kernel: Double-free in split_…</p> https://cve.radiocsirt.org/vuln/rhsa-2023:2951 https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49653 <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 92 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: i2c: piix4: Fix a memory leak in the EFCH MMIO support The recently added support for EFCH MMIO regions introduced a memory leak in that code path. The leak is caused by the fact that release_resource() merely removes the resource from the tree but does not free its memory. We need to call release_mem_region() instead, which does free the memory. As a nice side effect, this brings back some symmetry between the legacy and MMIO paths.</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 92 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: i2c: piix4: Fix a memory leak in the EFCH MMIO support The recently added support for EFCH MMIO regions introduced a memory leak in that code path. The leak is caused by the fact that release_resource() merely removes the resource from the tree but does not free its memory. We need to call release_mem_region() instead, which does free the memory. As a nice side effect, this brings back some symmetry between the legacy and MMIO paths.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49653