<?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>Tue, 29 Sep 2026 08:43:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89516 — sched_ext: Don't BUG_ON a destroyed DSQ in process_deferred_reenq_users</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89516</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 BUG_ON a destroyed DSQ in process_deferred_reenq_users&lt;/p&gt;
&lt;p&gt;scx_bpf_dsq_reenq() queues a deferred reenq (dru) that runs from
run_deferred(), not ops.dispatch(). If the DSQ is destroyed before the dru
runs, process_deferred_reenq_users() sees dsq-&amp;gt;id == SCX_DSQ_INVALID and
hits the BUG_ON. destroy_dsq() doesn&amp;#39;t flush pending drus, so just skip.&lt;/p&gt;
&lt;p&gt;tj: Read dsq-&amp;gt;id once with READ_ONCE(). Reading it separately in the INVALID
    check and the BUG_ON would leave a window where destroy_dsq() can
    invalidate the id between the two reads and still trigger the BUG_ON.&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 BUG_ON a destroyed DSQ in process_deferred_reenq_users&lt;/p&gt;
&lt;p&gt;scx_bpf_dsq_reenq() queues a deferred reenq (dru) that runs from
run_deferred(), not ops.dispatch(). If the DSQ is destroyed before the dru
runs, process_deferred_reenq_users() sees dsq-&amp;gt;id == SCX_DSQ_INVALID and
hits the BUG_ON. destroy_dsq() doesn&amp;#39;t flush pending drus, so just skip.&lt;/p&gt;
&lt;p&gt;tj: Read dsq-&amp;gt;id once with READ_ONCE(). Reading it separately in the INVALID
    check and the BUG_ON would leave a window where destroy_dsq() can
    invalidate the id between the two reads and still trigger the BUG_ON.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89516</guid>
    </item>
  </channel>
</rss>
