https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 13:00:10 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-12046 bdu:2025-12046 https://cve.radiocsirt.org/vuln/bdu:2025-12046 https://cve.radiocsirt.org/vuln/bell-cve-2025-21770 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-21770 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587 https://cve.radiocsirt.org/vuln/euvd-2026-314033 EUVD-2026-314033 https://cve.radiocsirt.org/vuln/euvd-2026-314033 https://cve.radiocsirt.org/vuln/fkie_cve-2025-21770 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Fix potential memory leak in iopf_queue_remove_device()</p> <p>The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf&#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue.</p> <p>However, it fails to release the group structure that represents a group of iopf&#39;s awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf&#39;s.</p> <p>Fix it by calling iopf_free_group() after the iopf group is responded.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Fix potential memory leak in iopf_queue_remove_device()</p> <p>The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf&#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue.</p> <p>However, it fails to release the group structure that represents a group of iopf&#39;s awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf&#39;s.</p> <p>Fix it by calling iopf_free_group() after the iopf group is responded.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-21770 https://cve.radiocsirt.org/vuln/ghsa-9q42-qq54-fwvj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Fix potential memory leak in iopf_queue_remove_device()</p> <p>The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf&#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue.</p> <p>However, it fails to release the group structure that represents a group of iopf&#39;s awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf&#39;s.</p> <p>Fix it by calling iopf_free_group() after the iopf group is responded.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Fix potential memory leak in iopf_queue_remove_device()</p> <p>The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf&#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue.</p> <p>However, it fails to release the group structure that represents a group of iopf&#39;s awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf&#39;s.</p> <p>Fix it by calling iopf_free_group() after the iopf group is responded.</p> https://cve.radiocsirt.org/vuln/ghsa-9q42-qq54-fwvj https://cve.radiocsirt.org/vuln/suse-su-2025:02333-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:02333-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21770 <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 75 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: iommu: Fix potential memory leak in iopf_queue_remove_device() The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf&#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue. However, it fails to release the group structure that represents a group of iopf&#39;s awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf&#39;s. Fix it by calling iopf_free_group() after the iopf group is responded.</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 75 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: iommu: Fix potential memory leak in iopf_queue_remove_device() The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf&#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue. However, it fails to release the group structure that represents a group of iopf&#39;s awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf&#39;s. Fix it by calling iopf_free_group() after the iopf group is responded.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21770 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0453 <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.</p> <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0453