https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 22:22:11 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-03852 bdu:2026-03852 https://cve.radiocsirt.org/vuln/bdu:2026-03852 https://cve.radiocsirt.org/vuln/bell-cve-2023-52981 <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-2023-52981 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0449 certfr-2025-avi-0449 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0449 https://cve.radiocsirt.org/vuln/euvd-2026-345110 EUVD-2026-345110 https://cve.radiocsirt.org/vuln/euvd-2026-345110 https://cve.radiocsirt.org/vuln/fkie_cve-2023-52981 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/i915: Fix request ref counting during error capture &amp; debugfs dump</p> <p>When GuC support was added to error capture, the reference counting around the request object was broken. Fix it up.</p> <p>The context based search manages the spinlocking around the search internally. So it needs to grab the reference count internally as well. The execlist only request based search relies on external locking, so it needs an external reference count but within the spinlock not outside it.</p> <p>The only other caller of the context based search is the code for dumping engine state to debugfs. That code wasn&#39;t previously getting an explicit reference at all as it does everything while holding the execlist specific spinlock. So, that needs updaing as well as that spinlock doesn&#39;t help when using GuC submission. Rather than trying to conditionally get/put depending on submission model, just change it to always do the get/put.</p> <p>v2: Explicitly document adding an extra blank line in some dense code (Andy Shevchenko). Fix multiple potential null pointer derefs in case of no request found (some spotted by Tvrtko, but there was more!). Also fix a leaked request in case of !started and another in __guc_reset_context now that intel_context_find_active_request is actually reference counting the returned request. v3: Add a _get suffix to intel_context_find_active_request now that it grabs a reference (Daniele). v4: Split the intel_guc_find_hun…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/i915: Fix request ref counting during error capture &amp; debugfs dump</p> <p>When GuC support was added to error capture, the reference counting around the request object was broken. Fix it up.</p> <p>The context based search manages the spinlocking around the search internally. So it needs to grab the reference count internally as well. The execlist only request based search relies on external locking, so it needs an external reference count but within the spinlock not outside it.</p> <p>The only other caller of the context based search is the code for dumping engine state to debugfs. That code wasn&#39;t previously getting an explicit reference at all as it does everything while holding the execlist specific spinlock. So, that needs updaing as well as that spinlock doesn&#39;t help when using GuC submission. Rather than trying to conditionally get/put depending on submission model, just change it to always do the get/put.</p> <p>v2: Explicitly document adding an extra blank line in some dense code (Andy Shevchenko). Fix multiple potential null pointer derefs in case of no request found (some spotted by Tvrtko, but there was more!). Also fix a leaked request in case of !started and another in __guc_reset_context now that intel_context_find_active_request is actually reference counting the returned request. v3: Add a _get suffix to intel_context_find_active_request now that it grabs a reference (Daniele). v4: Split the intel_guc_find_hun…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-52981 https://cve.radiocsirt.org/vuln/ghsa-73pj-2jcm-q7xj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/i915: Fix request ref counting during error capture &amp; debugfs dump</p> <p>When GuC support was added to error capture, the reference counting around the request object was broken. Fix it up.</p> <p>The context based search manages the spinlocking around the search internally. So it needs to grab the reference count internally as well. The execlist only request based search relies on external locking, so it needs an external reference count but within the spinlock not outside it.</p> <p>The only other caller of the context based search is the code for dumping engine state to debugfs. That code wasn&#39;t previously getting an explicit reference at all as it does everything while holding the execlist specific spinlock. So, that needs updaing as well as that spinlock doesn&#39;t help when using GuC submission. Rather than trying to conditionally get/put depending on submission model, just change it to always do the get/put.</p> <p>v2: Explicitly document adding an extra blank line in some dense code (Andy Shevchenko). Fix multiple potential null pointer derefs in case of no request found (some spotted by Tvrtko, but there was more!). Also fix a leaked request in case of !started and another in __guc_reset_context now that intel_context_find_active_request is actually reference counting the returned request. v3: Add a _get suffix to intel_context_find_active_request now that it grabs a reference (Daniele). v4: Split the intel_guc_find_hun…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/i915: Fix request ref counting during error capture &amp; debugfs dump</p> <p>When GuC support was added to error capture, the reference counting around the request object was broken. Fix it up.</p> <p>The context based search manages the spinlocking around the search internally. So it needs to grab the reference count internally as well. The execlist only request based search relies on external locking, so it needs an external reference count but within the spinlock not outside it.</p> <p>The only other caller of the context based search is the code for dumping engine state to debugfs. That code wasn&#39;t previously getting an explicit reference at all as it does everything while holding the execlist specific spinlock. So, that needs updaing as well as that spinlock doesn&#39;t help when using GuC submission. Rather than trying to conditionally get/put depending on submission model, just change it to always do the get/put.</p> <p>v2: Explicitly document adding an extra blank line in some dense code (Andy Shevchenko). Fix multiple potential null pointer derefs in case of no request found (some spotted by Tvrtko, but there was more!). Also fix a leaked request in case of !started and another in __guc_reset_context now that intel_context_find_active_request is actually reference counting the returned request. v3: Add a _get suffix to intel_context_find_active_request now that it grabs a reference (Daniele). v4: Split the intel_guc_find_hun…</p> https://cve.radiocsirt.org/vuln/ghsa-73pj-2jcm-q7xj https://cve.radiocsirt.org/vuln/msrc_cve-2023-52981 msrc_CVE-2023-52981 https://cve.radiocsirt.org/vuln/msrc_cve-2023-52981 https://cve.radiocsirt.org/vuln/rhsa-2023:6583 <p>security update for kernel</p> <p>security update for kernel</p> https://cve.radiocsirt.org/vuln/rhsa-2023:6583 https://cve.radiocsirt.org/vuln/suse-su-2025:01620-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:01620-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52981 <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 109 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/i915: Fix request ref counting during error capture &amp; debugfs dump When GuC support was added to error capture, the reference counting around the request object was broken. Fix it up. The context based search manages the spinlocking around the search internally. So it needs to grab the reference count internally as well. The execlist only request based search relies on external locking, so it needs an external reference count but within the spinlock not outside it. The only other caller of the context based search is the code for dumping engine state to debugfs. That code wasn&#39;t previously getting an explicit reference at all as it does everything while holding the execlist specific spinlock. So, that needs updaing as well as that spinlock doesn&#39;t help when using GuC submission. Rather than trying to conditionally get/put depending on submission model, just change it to always do the get/put. v2: Explicitly document adding an extra blank line in some dense code (Andy Shevchenko). Fix multiple potential null pointer derefs in case of no request found (some spotted by Tvrtko, but there was more!). Also fix a leaked request in case of !started and another in __guc_reset_context now that intel_context_find_active_request is actually reference counting the returned request. v3: Add a _get suffix to intel_context_find_active_request now that it grabs a reference (Daniele). v4: Split the intel_guc_find_hung_con…</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 109 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/i915: Fix request ref counting during error capture &amp; debugfs dump When GuC support was added to error capture, the reference counting around the request object was broken. Fix it up. The context based search manages the spinlocking around the search internally. So it needs to grab the reference count internally as well. The execlist only request based search relies on external locking, so it needs an external reference count but within the spinlock not outside it. The only other caller of the context based search is the code for dumping engine state to debugfs. That code wasn&#39;t previously getting an explicit reference at all as it does everything while holding the execlist specific spinlock. So, that needs updaing as well as that spinlock doesn&#39;t help when using GuC submission. Rather than trying to conditionally get/put depending on submission model, just change it to always do the get/put. v2: Explicitly document adding an extra blank line in some dense code (Andy Shevchenko). Fix multiple potential null pointer derefs in case of no request found (some spotted by Tvrtko, but there was more!). Also fix a leaked request in case of !started and another in __guc_reset_context now that intel_context_find_active_request is actually reference counting the returned request. v3: Add a _get suffix to intel_context_find_active_request now that it grabs a reference (Daniele). v4: Split the intel_guc_find_hung_con…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52981 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649