https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 08:07:06 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13905 bdu:2025-13905 https://cve.radiocsirt.org/vuln/bdu:2025-13905 https://cve.radiocsirt.org/vuln/bell-cve-2024-50144 <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-50144 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/cnvd-2024-46399 cnvd-2024-46399 https://cve.radiocsirt.org/vuln/cnvd-2024-46399 https://cve.radiocsirt.org/vuln/euvd-2026-313505 EUVD-2026-313505 https://cve.radiocsirt.org/vuln/euvd-2026-313505 https://cve.radiocsirt.org/vuln/fkie_cve-2024-50144 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/xe: fix unbalanced rpm put() with fence_fini()</p> <p>Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn&#39;t. It looks like we can just drop the fini() call since the fence signaller side will already call this for us.</p> <p>There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate.</p> <p>v2 (Matt B): - Prefer warning if we detect double fini()</p> <p>(cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/xe: fix unbalanced rpm put() with fence_fini()</p> <p>Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn&#39;t. It looks like we can just drop the fini() call since the fence signaller side will already call this for us.</p> <p>There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate.</p> <p>v2 (Matt B): - Prefer warning if we detect double fini()</p> <p>(cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183)</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-50144 https://cve.radiocsirt.org/vuln/ghsa-cjjp-gcwg-8fxm <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/xe: fix unbalanced rpm put() with fence_fini()</p> <p>Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn&#39;t. It looks like we can just drop the fini() call since the fence signaller side will already call this for us.</p> <p>There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate.</p> <p>v2 (Matt B): - Prefer warning if we detect double fini()</p> <p>(cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/xe: fix unbalanced rpm put() with fence_fini()</p> <p>Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn&#39;t. It looks like we can just drop the fini() call since the fence signaller side will already call this for us.</p> <p>There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate.</p> <p>v2 (Matt B): - Prefer warning if we detect double fini()</p> <p>(cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183)</p> https://cve.radiocsirt.org/vuln/ghsa-cjjp-gcwg-8fxm https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 <p>kernel-devel-6.11.8-1.1 on GA media</p> <p>kernel-devel-6.11.8-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50144 <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 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/xe: fix unbalanced rpm put() with fence_fini() Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn&#39;t. It looks like we can just drop the fini() call since the fence signaller side will already call this for us. There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate. v2 (Matt B): - Prefer warning if we detect double fini() (cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183)</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 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/xe: fix unbalanced rpm put() with fence_fini() Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn&#39;t. It looks like we can just drop the fini() call since the fence signaller side will already call this for us. There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate. v2 (Matt B): - Prefer warning if we detect double fini() (cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183)</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50144 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3367 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3367