<?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://vulnerability.circl.lu</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, 02 Oct 2026 18:33:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39780 — sched/ext: Fix invalid task state transitions on class switch</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39780</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2025-39780</guid>
    </item>
  </channel>
</rss>
