<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 17 Nov 2026 10:09:12 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99005</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99005</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99005</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1470 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1470</link>
      <description>certfr-2026-avi-1470</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1470</guid>
    </item>
    <item>
      <title>EUVD-2026-396120</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396120</link>
      <description>EUVD-2026-396120</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396120</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99005</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99005</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Unmask interrupts only when ACTIVE is true&lt;/p&gt;
&lt;p&gt;There is a small race window between intel_rps_boost() reading
a stale ACTIVE state and queuing rps-&amp;gt;work, where ACTIVE may be
changed via asynchronous calls triggered by wakeref drop.
This means that rps_work() could be triggered after the GT has
been parked, so unmasking RPS PM interrupts would happen without
holding PM wakelock. This sequence of events may be observed
during live_rc6_ctx_wa() selftest:&lt;/p&gt;
&lt;p&gt;1) live_rc6_ctx_wa()
   -&amp;gt; intel_engine_pm_put()
      -&amp;gt; wakeref_put()&lt;/p&gt;
&lt;p&gt;ASYNC1) wakeref_put() callback
          -&amp;gt; __engine_park()
             -&amp;gt; intel_gt_pm_put_async()
                -&amp;gt; intel_gt_pm_put_async_untracked()
                   -&amp;gt; intel_wakeref_put_async()&lt;/p&gt;
&lt;p&gt;ASYNC2) wakeref_put_async() callback
          -&amp;gt; __gt_park()
             -&amp;gt; intel_rps_park()
                -&amp;gt; intel_rps_clear_active() [clear ACTIVE]
                WITH INTERRUPTS:
                -&amp;gt; rps_disable_interrupts()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)
                   -&amp;gt; rps_reset_interrupts() [rps-&amp;gt;pm_iir = 0]
                WITHOUT INTERRUPTS (TIMER mode):
                -&amp;gt; rps_stop_timer()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)&lt;/p&gt;
&lt;p&gt;2) live_rc6_ctx_wa()
   -&amp;gt; intel_gt_wait_for_idle()
      -&amp;gt; intel_gt_retire_requests_timeout()
         -&amp;gt; dma_fence_wait_timeout()
            -&amp;gt; ops-&amp;gt;wait() [i915_fence_wait()]
               -&amp;gt; i915_reque…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Unmask interrupts only when ACTIVE is true&lt;/p&gt;
&lt;p&gt;There is a small race window between intel_rps_boost() reading
a stale ACTIVE state and queuing rps-&amp;gt;work, where ACTIVE may be
changed via asynchronous calls triggered by wakeref drop.
This means that rps_work() could be triggered after the GT has
been parked, so unmasking RPS PM interrupts would happen without
holding PM wakelock. This sequence of events may be observed
during live_rc6_ctx_wa() selftest:&lt;/p&gt;
&lt;p&gt;1) live_rc6_ctx_wa()
   -&amp;gt; intel_engine_pm_put()
      -&amp;gt; wakeref_put()&lt;/p&gt;
&lt;p&gt;ASYNC1) wakeref_put() callback
          -&amp;gt; __engine_park()
             -&amp;gt; intel_gt_pm_put_async()
                -&amp;gt; intel_gt_pm_put_async_untracked()
                   -&amp;gt; intel_wakeref_put_async()&lt;/p&gt;
&lt;p&gt;ASYNC2) wakeref_put_async() callback
          -&amp;gt; __gt_park()
             -&amp;gt; intel_rps_park()
                -&amp;gt; intel_rps_clear_active() [clear ACTIVE]
                WITH INTERRUPTS:
                -&amp;gt; rps_disable_interrupts()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)
                   -&amp;gt; rps_reset_interrupts() [rps-&amp;gt;pm_iir = 0]
                WITHOUT INTERRUPTS (TIMER mode):
                -&amp;gt; rps_stop_timer()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)&lt;/p&gt;
&lt;p&gt;2) live_rc6_ctx_wa()
   -&amp;gt; intel_gt_wait_for_idle()
      -&amp;gt; intel_gt_retire_requests_timeout()
         -&amp;gt; dma_fence_wait_timeout()
            -&amp;gt; ops-&amp;gt;wait() [i915_fence_wait()]
               -&amp;gt; i915_reque…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99005</guid>
    </item>
    <item>
      <title>GHSA-vcpf-23w8-q6wv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vcpf-23w8-q6wv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Unmask interrupts only when ACTIVE is true&lt;/p&gt;
&lt;p&gt;There is a small race window between intel_rps_boost() reading
a stale ACTIVE state and queuing rps-&amp;gt;work, where ACTIVE may be
changed via asynchronous calls triggered by wakeref drop.
This means that rps_work() could be triggered after the GT has
been parked, so unmasking RPS PM interrupts would happen without
holding PM wakelock. This sequence of events may be observed
during live_rc6_ctx_wa() selftest:&lt;/p&gt;
&lt;p&gt;1) live_rc6_ctx_wa()
   -&amp;gt; intel_engine_pm_put()
      -&amp;gt; wakeref_put()&lt;/p&gt;
&lt;p&gt;ASYNC1) wakeref_put() callback
          -&amp;gt; __engine_park()
             -&amp;gt; intel_gt_pm_put_async()
                -&amp;gt; intel_gt_pm_put_async_untracked()
                   -&amp;gt; intel_wakeref_put_async()&lt;/p&gt;
&lt;p&gt;ASYNC2) wakeref_put_async() callback
          -&amp;gt; __gt_park()
             -&amp;gt; intel_rps_park()
                -&amp;gt; intel_rps_clear_active() [clear ACTIVE]
                WITH INTERRUPTS:
                -&amp;gt; rps_disable_interrupts()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)
                   -&amp;gt; rps_reset_interrupts() [rps-&amp;gt;pm_iir = 0]
                WITHOUT INTERRUPTS (TIMER mode):
                -&amp;gt; rps_stop_timer()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)&lt;/p&gt;
&lt;p&gt;2) live_rc6_ctx_wa()
   -&amp;gt; intel_gt_wait_for_idle()
      -&amp;gt; intel_gt_retire_requests_timeout()
         -&amp;gt; dma_fence_wait_timeout()
            -&amp;gt; ops-&amp;gt;wait() [i915_fence_wait()]
               -&amp;gt; i915_reque…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/i915/gt: Unmask interrupts only when ACTIVE is true&lt;/p&gt;
&lt;p&gt;There is a small race window between intel_rps_boost() reading
a stale ACTIVE state and queuing rps-&amp;gt;work, where ACTIVE may be
changed via asynchronous calls triggered by wakeref drop.
This means that rps_work() could be triggered after the GT has
been parked, so unmasking RPS PM interrupts would happen without
holding PM wakelock. This sequence of events may be observed
during live_rc6_ctx_wa() selftest:&lt;/p&gt;
&lt;p&gt;1) live_rc6_ctx_wa()
   -&amp;gt; intel_engine_pm_put()
      -&amp;gt; wakeref_put()&lt;/p&gt;
&lt;p&gt;ASYNC1) wakeref_put() callback
          -&amp;gt; __engine_park()
             -&amp;gt; intel_gt_pm_put_async()
                -&amp;gt; intel_gt_pm_put_async_untracked()
                   -&amp;gt; intel_wakeref_put_async()&lt;/p&gt;
&lt;p&gt;ASYNC2) wakeref_put_async() callback
          -&amp;gt; __gt_park()
             -&amp;gt; intel_rps_park()
                -&amp;gt; intel_rps_clear_active() [clear ACTIVE]
                WITH INTERRUPTS:
                -&amp;gt; rps_disable_interrupts()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)
                   -&amp;gt; rps_reset_interrupts() [rps-&amp;gt;pm_iir = 0]
                WITHOUT INTERRUPTS (TIMER mode):
                -&amp;gt; rps_stop_timer()
                   -&amp;gt; cancel_work_sync(rps-&amp;gt;work)&lt;/p&gt;
&lt;p&gt;2) live_rc6_ctx_wa()
   -&amp;gt; intel_gt_wait_for_idle()
      -&amp;gt; intel_gt_retire_requests_timeout()
         -&amp;gt; dma_fence_wait_timeout()
            -&amp;gt; ops-&amp;gt;wait() [i915_fence_wait()]
               -&amp;gt; i915_reque…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vcpf-23w8-q6wv</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99005 — drm/i915/gt: Unmask interrupts only when ACTIVE is true</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99005</link>
      <description>msrc_CVE-2026-99005</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99005</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99005</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99005</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Unmask interrupts only when ACTIVE is true There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps-&amp;gt;work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest: 1) live_rc6_ctx_wa()    -&amp;gt; intel_engine_pm_put()       -&amp;gt; wakeref_put() ASYNC1) wakeref_put() callback           -&amp;gt; __engine_park()              -&amp;gt; intel_gt_pm_put_async()                 -&amp;gt; intel_gt_pm_put_async_untracked()                    -&amp;gt; intel_wakeref_put_async() ASYNC2) wakeref_put_async() callback           -&amp;gt; __gt_park()              -&amp;gt; intel_rps_park()                 -&amp;gt; intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -&amp;gt; rps_disable_interrupts()                    -&amp;gt; cancel_work_sync(rps-&amp;gt;work)                    -&amp;gt; rps_reset_interrupts() [rps-&amp;gt;pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -&amp;gt; rps_stop_timer()                    -&amp;gt; cancel_work_sync(rps-&amp;gt;work) 2) live_rc6_ctx_wa()    -&amp;gt; intel_gt_wait_for_idle()       -&amp;gt; intel_gt_retire_requests_timeout()          -&amp;gt; dma_fence_wait_timeout()             -&amp;gt; ops-&amp;gt;wait() [i915_fence_wait()]                -&amp;gt; i915_request_wai…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Unmask interrupts only when ACTIVE is true There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps-&amp;gt;work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest: 1) live_rc6_ctx_wa()    -&amp;gt; intel_engine_pm_put()       -&amp;gt; wakeref_put() ASYNC1) wakeref_put() callback           -&amp;gt; __engine_park()              -&amp;gt; intel_gt_pm_put_async()                 -&amp;gt; intel_gt_pm_put_async_untracked()                    -&amp;gt; intel_wakeref_put_async() ASYNC2) wakeref_put_async() callback           -&amp;gt; __gt_park()              -&amp;gt; intel_rps_park()                 -&amp;gt; intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -&amp;gt; rps_disable_interrupts()                    -&amp;gt; cancel_work_sync(rps-&amp;gt;work)                    -&amp;gt; rps_reset_interrupts() [rps-&amp;gt;pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -&amp;gt; rps_stop_timer()                    -&amp;gt; cancel_work_sync(rps-&amp;gt;work) 2) live_rc6_ctx_wa()    -&amp;gt; intel_gt_wait_for_idle()       -&amp;gt; intel_gt_retire_requests_timeout()          -&amp;gt; dma_fence_wait_timeout()             -&amp;gt; ops-&amp;gt;wait() [i915_fence_wait()]                -&amp;gt; i915_request_wai…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99005</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
