<?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>Sat, 10 Oct 2026 21:52:55 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03109</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03109</link>
      <description>bdu:2026-03109</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03109</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38522</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38522</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38522</guid>
    </item>
    <item>
      <title>EUVD-2026-314643</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314643</link>
      <description>EUVD-2026-314643</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314643</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38522</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38522</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/ext: Prevent update_locked_rq() calls with NULL rq&lt;/p&gt;
&lt;p&gt;Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL
in the SCX_CALL_OP and SCX_CALL_OP_RET macros.&lt;/p&gt;
&lt;p&gt;Previously, calling update_locked_rq(NULL) with preemption enabled could
trigger the following warning:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_write() in preemptible [00000000]&lt;/p&gt;
&lt;p&gt;This happens because __this_cpu_write() is unsafe to use in preemptible
context.&lt;/p&gt;
&lt;p&gt;rq is NULL when an ops invoked from an unlocked context. In such cases, we
don&amp;#39;t need to store any rq, since the value should already be NULL
(unlocked). Ensure that update_locked_rq() is only called when rq is
non-NULL, preventing calling __this_cpu_write() on preemptible context.&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;sched/ext: Prevent update_locked_rq() calls with NULL rq&lt;/p&gt;
&lt;p&gt;Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL
in the SCX_CALL_OP and SCX_CALL_OP_RET macros.&lt;/p&gt;
&lt;p&gt;Previously, calling update_locked_rq(NULL) with preemption enabled could
trigger the following warning:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_write() in preemptible [00000000]&lt;/p&gt;
&lt;p&gt;This happens because __this_cpu_write() is unsafe to use in preemptible
context.&lt;/p&gt;
&lt;p&gt;rq is NULL when an ops invoked from an unlocked context. In such cases, we
don&amp;#39;t need to store any rq, since the value should already be NULL
(unlocked). Ensure that update_locked_rq() is only called when rq is
non-NULL, preventing calling __this_cpu_write() on preemptible context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38522</guid>
    </item>
    <item>
      <title>GHSA-8mqg-35g3-7pvm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8mqg-35g3-7pvm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/ext: Prevent update_locked_rq() calls with NULL rq&lt;/p&gt;
&lt;p&gt;Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL
in the SCX_CALL_OP and SCX_CALL_OP_RET macros.&lt;/p&gt;
&lt;p&gt;Previously, calling update_locked_rq(NULL) with preemption enabled could
trigger the following warning:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_write() in preemptible [00000000]&lt;/p&gt;
&lt;p&gt;This happens because __this_cpu_write() is unsafe to use in preemptible
context.&lt;/p&gt;
&lt;p&gt;rq is NULL when an ops invoked from an unlocked context. In such cases, we
don&amp;#39;t need to store any rq, since the value should already be NULL
(unlocked). Ensure that update_locked_rq() is only called when rq is
non-NULL, preventing calling __this_cpu_write() on preemptible context.&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;sched/ext: Prevent update_locked_rq() calls with NULL rq&lt;/p&gt;
&lt;p&gt;Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL
in the SCX_CALL_OP and SCX_CALL_OP_RET macros.&lt;/p&gt;
&lt;p&gt;Previously, calling update_locked_rq(NULL) with preemption enabled could
trigger the following warning:&lt;/p&gt;
&lt;p&gt;BUG: using __this_cpu_write() in preemptible [00000000]&lt;/p&gt;
&lt;p&gt;This happens because __this_cpu_write() is unsafe to use in preemptible
context.&lt;/p&gt;
&lt;p&gt;rq is NULL when an ops invoked from an unlocked context. In such cases, we
don&amp;#39;t need to store any rq, since the value should already be NULL
(unlocked). Ensure that update_locked_rq() is only called when rq is
non-NULL, preventing calling __this_cpu_write() on preemptible context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8mqg-35g3-7pvm</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38522</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38522</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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/ext: Prevent update_locked_rq() calls with NULL rq Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL in the SCX_CALL_OP and SCX_CALL_OP_RET macros. Previously, calling update_locked_rq(NULL) with preemption enabled could trigger the following warning:     BUG: using __this_cpu_write() in preemptible [00000000] This happens because __this_cpu_write() is unsafe to use in preemptible context. rq is NULL when an ops invoked from an unlocked context. In such cases, we don&amp;#39;t need to store any rq, since the value should already be NULL (unlocked). Ensure that update_locked_rq() is only called when rq is non-NULL, preventing calling __this_cpu_write() on preemptible context.&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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/ext: Prevent update_locked_rq() calls with NULL rq Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL in the SCX_CALL_OP and SCX_CALL_OP_RET macros. Previously, calling update_locked_rq(NULL) with preemption enabled could trigger the following warning:     BUG: using __this_cpu_write() in preemptible [00000000] This happens because __this_cpu_write() is unsafe to use in preemptible context. rq is NULL when an ops invoked from an unlocked context. In such cases, we don&amp;#39;t need to store any rq, since the value should already be NULL (unlocked). Ensure that update_locked_rq() is only called when rq is non-NULL, preventing calling __this_cpu_write() on preemptible context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38522</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1858 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1858</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1858</guid>
    </item>
  </channel>
</rss>
