<?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>Fri, 09 Oct 2026 18:15:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15214</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15214</link>
      <description>bdu:2025-15214</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15214</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39780</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39780</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-39780</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>EUVD-2026-347200</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347200</link>
      <description>EUVD-2026-347200</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347200</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39780</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39780</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/ext: Fix invalid task state transitions on class switch&lt;/p&gt;
&lt;p&gt;When enabling a sched_ext scheduler, we may trigger invalid task state
transitions, resulting in warnings like the following (which can be
easily reproduced by running the hotplug selftest in a loop):&lt;/p&gt;
&lt;p&gt;sched_ext: Invalid task state transition 0 -&amp;gt; 3 for fish[770]
 WARNING: CPU: 18 PID: 787 at kernel/sched/ext.c:3862 scx_set_task_state+0x7c/0xc0
 ...
 RIP: 0010:scx_set_task_state+0x7c/0xc0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  scx_enable_task+0x11f/0x2e0
  switching_to_scx+0x24/0x110
  scx_enable.isra.0+0xd14/0x13d0
  bpf_struct_ops_link_create+0x136/0x1a0
  __sys_bpf+0x1edd/0x2c30
  __x64_sys_bpf+0x21/0x30
  do_syscall_64+0xbb/0x370
  entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;
&lt;p&gt;This happens because we skip initialization for tasks that are already
dead (with their usage counter set to zero), but we don&amp;#39;t exclude them
during the scheduling class transition phase.&lt;/p&gt;
&lt;p&gt;Fix this by also skipping dead tasks during class swiching, preventing
invalid task state transitions.&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: Fix invalid task state transitions on class switch&lt;/p&gt;
&lt;p&gt;When enabling a sched_ext scheduler, we may trigger invalid task state
transitions, resulting in warnings like the following (which can be
easily reproduced by running the hotplug selftest in a loop):&lt;/p&gt;
&lt;p&gt;sched_ext: Invalid task state transition 0 -&amp;gt; 3 for fish[770]
 WARNING: CPU: 18 PID: 787 at kernel/sched/ext.c:3862 scx_set_task_state+0x7c/0xc0
 ...
 RIP: 0010:scx_set_task_state+0x7c/0xc0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  scx_enable_task+0x11f/0x2e0
  switching_to_scx+0x24/0x110
  scx_enable.isra.0+0xd14/0x13d0
  bpf_struct_ops_link_create+0x136/0x1a0
  __sys_bpf+0x1edd/0x2c30
  __x64_sys_bpf+0x21/0x30
  do_syscall_64+0xbb/0x370
  entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;
&lt;p&gt;This happens because we skip initialization for tasks that are already
dead (with their usage counter set to zero), but we don&amp;#39;t exclude them
during the scheduling class transition phase.&lt;/p&gt;
&lt;p&gt;Fix this by also skipping dead tasks during class swiching, preventing
invalid task state transitions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39780</guid>
    </item>
    <item>
      <title>GHSA-6rhw-qcc5-9qm4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6rhw-qcc5-9qm4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/ext: Fix invalid task state transitions on class switch&lt;/p&gt;
&lt;p&gt;When enabling a sched_ext scheduler, we may trigger invalid task state
transitions, resulting in warnings like the following (which can be
easily reproduced by running the hotplug selftest in a loop):&lt;/p&gt;
&lt;p&gt;sched_ext: Invalid task state transition 0 -&amp;gt; 3 for fish[770]
 WARNING: CPU: 18 PID: 787 at kernel/sched/ext.c:3862 scx_set_task_state+0x7c/0xc0
 ...
 RIP: 0010:scx_set_task_state+0x7c/0xc0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  scx_enable_task+0x11f/0x2e0
  switching_to_scx+0x24/0x110
  scx_enable.isra.0+0xd14/0x13d0
  bpf_struct_ops_link_create+0x136/0x1a0
  __sys_bpf+0x1edd/0x2c30
  __x64_sys_bpf+0x21/0x30
  do_syscall_64+0xbb/0x370
  entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;
&lt;p&gt;This happens because we skip initialization for tasks that are already
dead (with their usage counter set to zero), but we don&amp;#39;t exclude them
during the scheduling class transition phase.&lt;/p&gt;
&lt;p&gt;Fix this by also skipping dead tasks during class swiching, preventing
invalid task state transitions.&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: Fix invalid task state transitions on class switch&lt;/p&gt;
&lt;p&gt;When enabling a sched_ext scheduler, we may trigger invalid task state
transitions, resulting in warnings like the following (which can be
easily reproduced by running the hotplug selftest in a loop):&lt;/p&gt;
&lt;p&gt;sched_ext: Invalid task state transition 0 -&amp;gt; 3 for fish[770]
 WARNING: CPU: 18 PID: 787 at kernel/sched/ext.c:3862 scx_set_task_state+0x7c/0xc0
 ...
 RIP: 0010:scx_set_task_state+0x7c/0xc0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  scx_enable_task+0x11f/0x2e0
  switching_to_scx+0x24/0x110
  scx_enable.isra.0+0xd14/0x13d0
  bpf_struct_ops_link_create+0x136/0x1a0
  __sys_bpf+0x1edd/0x2c30
  __x64_sys_bpf+0x21/0x30
  do_syscall_64+0xbb/0x370
  entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;
&lt;p&gt;This happens because we skip initialization for tasks that are already
dead (with their usage counter set to zero), but we don&amp;#39;t exclude them
during the scheduling class transition phase.&lt;/p&gt;
&lt;p&gt;Fix this by also skipping dead tasks during class swiching, preventing
invalid task state transitions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6rhw-qcc5-9qm4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39780</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39780</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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/ext: Fix invalid task state transitions on class switch When enabling a sched_ext scheduler, we may trigger invalid task state transitions, resulting in warnings like the following (which can be easily reproduced by running the hotplug selftest in a loop):  sched_ext: Invalid task state transition 0 -&amp;gt; 3 for fish[770]  WARNING: CPU: 18 PID: 787 at kernel/sched/ext.c:3862 scx_set_task_state+0x7c/0xc0  ...  RIP: 0010:scx_set_task_state+0x7c/0xc0  ...  Call Trace:   &amp;lt;TASK&amp;gt;   scx_enable_task+0x11f/0x2e0   switching_to_scx+0x24/0x110   scx_enable.isra.0+0xd14/0x13d0   bpf_struct_ops_link_create+0x136/0x1a0   __sys_bpf+0x1edd/0x2c30   __x64_sys_bpf+0x21/0x30   do_syscall_64+0xbb/0x370   entry_SYSCALL_64_after_hwframe+0x77/0x7f This happens because we skip initialization for tasks that are already dead (with their usage counter set to zero), but we don&amp;#39;t exclude them during the scheduling class transition phase. Fix this by also skipping dead tasks during class swiching, preventing invalid task state transitions.&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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/ext: Fix invalid task state transitions on class switch When enabling a sched_ext scheduler, we may trigger invalid task state transitions, resulting in warnings like the following (which can be easily reproduced by running the hotplug selftest in a loop):  sched_ext: Invalid task state transition 0 -&amp;gt; 3 for fish[770]  WARNING: CPU: 18 PID: 787 at kernel/sched/ext.c:3862 scx_set_task_state+0x7c/0xc0  ...  RIP: 0010:scx_set_task_state+0x7c/0xc0  ...  Call Trace:   &amp;lt;TASK&amp;gt;   scx_enable_task+0x11f/0x2e0   switching_to_scx+0x24/0x110   scx_enable.isra.0+0xd14/0x13d0   bpf_struct_ops_link_create+0x136/0x1a0   __sys_bpf+0x1edd/0x2c30   __x64_sys_bpf+0x21/0x30   do_syscall_64+0xbb/0x370   entry_SYSCALL_64_after_hwframe+0x77/0x7f This happens because we skip initialization for tasks that are already dead (with their usage counter set to zero), but we don&amp;#39;t exclude them during the scheduling class transition phase. Fix this by also skipping dead tasks during class swiching, preventing invalid task state transitions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39780</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2040 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2040</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Sicherheitsmechanismen zu umgehen, sowie einen Denial of Service Angriff oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Sicherheitsmechanismen zu umgehen, sowie einen Denial of Service Angriff oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2040</guid>
    </item>
  </channel>
</rss>
