<?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 14:05:52 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98864</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98864</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task&lt;/p&gt;
&lt;p&gt;ebf1ccff79c4 (&amp;#34;sched_ext: Fix ops.dequeue() semantics&amp;#34;) moved the final
ops_state store in scx_dispatch_enqueue() after the DSQ unlock so that the
custody update and ops.dequeue() precede it. A task can thus be found on a
DSQ while still SCX_OPSS_DISPATCHING.&lt;/p&gt;
&lt;p&gt;The dequeue and core-sched pick paths wait for the state to clear in
ops_dequeue() but the reenqueue paths don&amp;#39;t. A reenqueue in that window runs
ops.enqueue() and sets SCX_OPSS_QUEUED before the dispatch has completed.
The dispatcher&amp;#39;s final store then overwrites it with SCX_OPSS_NONE and
finish_dispatch() drops every later dispatch of the task.&lt;/p&gt;
&lt;p&gt;Wait for SCX_OPSS_DISPATCHING to clear before dequeueing a task for
reenqueue, the same way ops_dequeue() does.&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: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task&lt;/p&gt;
&lt;p&gt;ebf1ccff79c4 (&amp;#34;sched_ext: Fix ops.dequeue() semantics&amp;#34;) moved the final
ops_state store in scx_dispatch_enqueue() after the DSQ unlock so that the
custody update and ops.dequeue() precede it. A task can thus be found on a
DSQ while still SCX_OPSS_DISPATCHING.&lt;/p&gt;
&lt;p&gt;The dequeue and core-sched pick paths wait for the state to clear in
ops_dequeue() but the reenqueue paths don&amp;#39;t. A reenqueue in that window runs
ops.enqueue() and sets SCX_OPSS_QUEUED before the dispatch has completed.
The dispatcher&amp;#39;s final store then overwrites it with SCX_OPSS_NONE and
finish_dispatch() drops every later dispatch of the task.&lt;/p&gt;
&lt;p&gt;Wait for SCX_OPSS_DISPATCHING to clear before dequeueing a task for
reenqueue, the same way ops_dequeue() does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98864</guid>
    </item>
    <item>
      <title>GHSA-fpjr-j5w9-j6gm</title>
      <link>https://db.gcve.eu/vuln/ghsa-fpjr-j5w9-j6gm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task&lt;/p&gt;
&lt;p&gt;ebf1ccff79c4 (&amp;#34;sched_ext: Fix ops.dequeue() semantics&amp;#34;) moved the final
ops_state store in scx_dispatch_enqueue() after the DSQ unlock so that the
custody update and ops.dequeue() precede it. A task can thus be found on a
DSQ while still SCX_OPSS_DISPATCHING.&lt;/p&gt;
&lt;p&gt;The dequeue and core-sched pick paths wait for the state to clear in
ops_dequeue() but the reenqueue paths don&amp;#39;t. A reenqueue in that window runs
ops.enqueue() and sets SCX_OPSS_QUEUED before the dispatch has completed.
The dispatcher&amp;#39;s final store then overwrites it with SCX_OPSS_NONE and
finish_dispatch() drops every later dispatch of the task.&lt;/p&gt;
&lt;p&gt;Wait for SCX_OPSS_DISPATCHING to clear before dequeueing a task for
reenqueue, the same way ops_dequeue() does.&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: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task&lt;/p&gt;
&lt;p&gt;ebf1ccff79c4 (&amp;#34;sched_ext: Fix ops.dequeue() semantics&amp;#34;) moved the final
ops_state store in scx_dispatch_enqueue() after the DSQ unlock so that the
custody update and ops.dequeue() precede it. A task can thus be found on a
DSQ while still SCX_OPSS_DISPATCHING.&lt;/p&gt;
&lt;p&gt;The dequeue and core-sched pick paths wait for the state to clear in
ops_dequeue() but the reenqueue paths don&amp;#39;t. A reenqueue in that window runs
ops.enqueue() and sets SCX_OPSS_QUEUED before the dispatch has completed.
The dispatcher&amp;#39;s final store then overwrites it with SCX_OPSS_NONE and
finish_dispatch() drops every later dispatch of the task.&lt;/p&gt;
&lt;p&gt;Wait for SCX_OPSS_DISPATCHING to clear before dequeueing a task for
reenqueue, the same way ops_dequeue() does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fpjr-j5w9-j6gm</guid>
    </item>
  </channel>
</rss>
