https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 21:39:48 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-15104 bdu:2025-15104 https://cve.radiocsirt.org/vuln/bdu:2025-15104 https://cve.radiocsirt.org/vuln/bell-cve-2024-53084 <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-2024-53084 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152 certfr-2025-avi-0152 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152 https://cve.radiocsirt.org/vuln/euvd-2026-313607 EUVD-2026-313607 https://cve.radiocsirt.org/vuln/euvd-2026-313607 https://cve.radiocsirt.org/vuln/fkie_cve-2024-53084 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/imagination: Break an object reference loop</p> <p>When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it:</p> <p>PVR GEM Object GPU scheduler &#34;finished&#34; fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object</p> <p>The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop.</p> <p>To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/imagination: Break an object reference loop</p> <p>When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it:</p> <p>PVR GEM Object GPU scheduler &#34;finished&#34; fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object</p> <p>The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop.</p> <p>To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-53084 https://cve.radiocsirt.org/vuln/ghsa-7mjf-5rrm-399r <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/imagination: Break an object reference loop</p> <p>When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it:</p> <p>PVR GEM Object GPU scheduler &#34;finished&#34; fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object</p> <p>The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop.</p> <p>To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/imagination: Break an object reference loop</p> <p>When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it:</p> <p>PVR GEM Object GPU scheduler &#34;finished&#34; fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object</p> <p>The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop.</p> <p>To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.</p> https://cve.radiocsirt.org/vuln/ghsa-7mjf-5rrm-399r https://cve.radiocsirt.org/vuln/msrc_cve-2024-53084 msrc_CVE-2024-53084 https://cve.radiocsirt.org/vuln/msrc_cve-2024-53084 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53084 <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 104 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Break an object reference loop When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it: PVR GEM Object GPU scheduler &#34;finished&#34; fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop. To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.</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 104 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Break an object reference loop When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it: PVR GEM Object GPU scheduler &#34;finished&#34; fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop. To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53084 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3509 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3509