<?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://db.gcve.eu</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>Mon, 19 Oct 2026 12:35:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98865 — sched_ext: Don't run ops.dequeue() with a DSQ lock held</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98865</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: Don&amp;#39;t run ops.dequeue() with a DSQ lock held&lt;/p&gt;
&lt;p&gt;ops.dequeue() is invoked with the source user DSQ&amp;#39;s lock still held on
the consume and move paths (scx_consume_dispatch_q(),
move_task_between_dsqs()). A BPF scheduler which locks the source user
DSQ from ops.dequeue() - e.g. by iterating it with bpf_iter_scx_dsq -
self-deadlocks.&lt;/p&gt;
&lt;p&gt;ops.dequeue() can only call the &amp;#34;any&amp;#34; kfuncs and none of them can lock a
builtin DSQ, so the global and bypass paths can&amp;#39;t deadlock; however,
all DSQ locks share one lockdep class, so iterating any user DSQ from
ops.dequeue() on those paths trips the recursion check.&lt;/p&gt;
&lt;p&gt;Move the invocation after the DSQ unlock on all three paths.
SCX_TASK_IN_CUSTODY is cleared under the lock serializing the transfer
so that the callback is invoked exactly once.&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: Don&amp;#39;t run ops.dequeue() with a DSQ lock held&lt;/p&gt;
&lt;p&gt;ops.dequeue() is invoked with the source user DSQ&amp;#39;s lock still held on
the consume and move paths (scx_consume_dispatch_q(),
move_task_between_dsqs()). A BPF scheduler which locks the source user
DSQ from ops.dequeue() - e.g. by iterating it with bpf_iter_scx_dsq -
self-deadlocks.&lt;/p&gt;
&lt;p&gt;ops.dequeue() can only call the &amp;#34;any&amp;#34; kfuncs and none of them can lock a
builtin DSQ, so the global and bypass paths can&amp;#39;t deadlock; however,
all DSQ locks share one lockdep class, so iterating any user DSQ from
ops.dequeue() on those paths trips the recursion check.&lt;/p&gt;
&lt;p&gt;Move the invocation after the DSQ unlock on all three paths.
SCX_TASK_IN_CUSTODY is cleared under the lock serializing the transfer
so that the callback is invoked exactly once.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98865</guid>
    </item>
  </channel>
</rss>
