<?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>Thu, 01 Oct 2026 18:57:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23275 — io_uring: ensure ctx-&gt;rings is stable for task work flags manipulation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23275</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;io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation&lt;/p&gt;
&lt;p&gt;If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while
the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of
IORING_SQ_TASKRUN to happen in the small window of swapping into the
new rings and the old rings being freed.&lt;/p&gt;
&lt;p&gt;Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is
protected by RCU. The task work flags manipulation is inside RCU
already, and if the resize ring freeing is done post an RCU synchronize,
then there&amp;#39;s no need to add locking to the fast path of task work
additions.&lt;/p&gt;
&lt;p&gt;Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode
that supports ring resizing. If this ever changes, then they too need to
use the io_ctx_mark_taskrun() helper.&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;io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation&lt;/p&gt;
&lt;p&gt;If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while
the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of
IORING_SQ_TASKRUN to happen in the small window of swapping into the
new rings and the old rings being freed.&lt;/p&gt;
&lt;p&gt;Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is
protected by RCU. The task work flags manipulation is inside RCU
already, and if the resize ring freeing is done post an RCU synchronize,
then there&amp;#39;s no need to add locking to the fast path of task work
additions.&lt;/p&gt;
&lt;p&gt;Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode
that supports ring resizing. If this ever changes, then they too need to
use the io_ctx_mark_taskrun() helper.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23275</guid>
    </item>
  </channel>
</rss>
