<?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 12:29:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21897 — sched_ext: Fix pick_task_scx() picking non-queued tasks when it's called without balance()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21897</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 pick_task_scx() picking non-queued tasks when it&amp;#39;s called without balance()&lt;/p&gt;
&lt;p&gt;a6250aa251ea (&amp;#34;sched_ext: Handle cases where pick_task_scx() is called
without preceding balance_scx()&amp;#34;) added a workaround to handle the cases
where pick_task_scx() is called without prececing balance_scx() which is due
to a fair class bug where pick_taks_fair() may return NULL after a true
return from balance_fair().&lt;/p&gt;
&lt;p&gt;The workaround detects when pick_task_scx() is called without preceding
balance_scx() and emulates SCX_RQ_BAL_KEEP and triggers kicking to avoid
stalling. Unfortunately, the workaround code was testing whether @prev was
on SCX to decide whether to keep the task running. This is incorrect as the
task may be on SCX but no longer runnable.&lt;/p&gt;
&lt;p&gt;This could lead to a non-runnable task to be returned from pick_task_scx()
which cause interesting confusions and failures. e.g. A common failure mode
is the task ending up with (!on_rq &amp;amp;&amp;amp; on_cpu) state which can cause
potential wakers to busy loop, which can easily lead to deadlocks.&lt;/p&gt;
&lt;p&gt;Fix it by testing whether @prev has SCX_TASK_QUEUED set. This makes
@prev_on_scx only used in one place. Open code the usage and improve the
comment while at it.&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 pick_task_scx() picking non-queued tasks when it&amp;#39;s called without balance()&lt;/p&gt;
&lt;p&gt;a6250aa251ea (&amp;#34;sched_ext: Handle cases where pick_task_scx() is called
without preceding balance_scx()&amp;#34;) added a workaround to handle the cases
where pick_task_scx() is called without prececing balance_scx() which is due
to a fair class bug where pick_taks_fair() may return NULL after a true
return from balance_fair().&lt;/p&gt;
&lt;p&gt;The workaround detects when pick_task_scx() is called without preceding
balance_scx() and emulates SCX_RQ_BAL_KEEP and triggers kicking to avoid
stalling. Unfortunately, the workaround code was testing whether @prev was
on SCX to decide whether to keep the task running. This is incorrect as the
task may be on SCX but no longer runnable.&lt;/p&gt;
&lt;p&gt;This could lead to a non-runnable task to be returned from pick_task_scx()
which cause interesting confusions and failures. e.g. A common failure mode
is the task ending up with (!on_rq &amp;amp;&amp;amp; on_cpu) state which can cause
potential wakers to busy loop, which can easily lead to deadlocks.&lt;/p&gt;
&lt;p&gt;Fix it by testing whether @prev has SCX_TASK_QUEUED set. This makes
@prev_on_scx only used in one place. Open code the usage and improve the
comment while at it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21897</guid>
    </item>
  </channel>
</rss>
