https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 20:50:44 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-04410 bdu:2026-04410 https://cve.radiocsirt.org/vuln/bdu:2026-04410 https://cve.radiocsirt.org/vuln/bell-cve-2025-39939 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-39939 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1164 certfr-2026-avi-1164 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1164 https://cve.radiocsirt.org/vuln/euvd-2026-347259 EUVD-2026-347259 https://cve.radiocsirt.org/vuln/euvd-2026-347259 https://cve.radiocsirt.org/vuln/fkie_cve-2025-39939 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/s390: Fix memory corruption when using identity domain</p> <p>zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero&#39;d initially and read on-demand later via a sysfs read. These counters aren&#39;t necessary for the identity domain; just return NULL in this case.</p> <p>This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/s390: Fix memory corruption when using identity domain</p> <p>zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero&#39;d initially and read on-demand later via a sysfs read. These counters aren&#39;t necessary for the identity domain; just return NULL in this case.</p> <p>This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-39939 https://cve.radiocsirt.org/vuln/ghsa-pm9c-rrjm-4v2f <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/s390: Fix memory corruption when using identity domain</p> <p>zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero&#39;d initially and read on-demand later via a sysfs read. These counters aren&#39;t necessary for the identity domain; just return NULL in this case.</p> <p>This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/s390: Fix memory corruption when using identity domain</p> <p>zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero&#39;d initially and read on-demand later via a sysfs read. These counters aren&#39;t necessary for the identity domain; just return NULL in this case.</p> <p>This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.</p> https://cve.radiocsirt.org/vuln/ghsa-pm9c-rrjm-4v2f https://cve.radiocsirt.org/vuln/suse-su-2026:4120-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:4120-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39939 <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 79 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Fix memory corruption when using identity domain zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero&#39;d initially and read on-demand later via a sysfs read. These counters aren&#39;t necessary for the identity domain; just return NULL in this case. This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.</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 79 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Fix memory corruption when using identity domain zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero&#39;d initially and read on-demand later via a sysfs read. These counters aren&#39;t necessary for the identity domain; just return NULL in this case. This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39939 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2194 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2194