<?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, 06 Oct 2026 07:08:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-81010 — io_uring/waitid: honor task_work cancellation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-81010</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/waitid: honor task_work cancellation&lt;/p&gt;
&lt;p&gt;io_waitid_cb() may run through the fallback task_work path when
task_work_add() can no longer queue work to the originating task. The
fallback runs from a kworker and io_uring marks such task work as
canceled through tw.cancel.&lt;/p&gt;
&lt;p&gt;io_waitid_cb() currently ignores tw.cancel and calls __do_wait().
waitid is task-context dependent: __do_wait() performs child lookup
relative to current, and the retry path also uses
current-&amp;gt;signal-&amp;gt;wait_chldexit. If the callback runs from the fallback
kworker, current is therefore not the task that submitted the request.&lt;/p&gt;
&lt;p&gt;Honor tw.cancel before entering __do_wait(). Complete the request with
-ECANCELED and skip the siginfo copy, since canceled task work may run
without the submitting task&amp;#39;s userspace execution context.&lt;/p&gt;
&lt;p&gt;Keep the existing siginfo handling for normal waitid completion and
explicit cancellation.&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/waitid: honor task_work cancellation&lt;/p&gt;
&lt;p&gt;io_waitid_cb() may run through the fallback task_work path when
task_work_add() can no longer queue work to the originating task. The
fallback runs from a kworker and io_uring marks such task work as
canceled through tw.cancel.&lt;/p&gt;
&lt;p&gt;io_waitid_cb() currently ignores tw.cancel and calls __do_wait().
waitid is task-context dependent: __do_wait() performs child lookup
relative to current, and the retry path also uses
current-&amp;gt;signal-&amp;gt;wait_chldexit. If the callback runs from the fallback
kworker, current is therefore not the task that submitted the request.&lt;/p&gt;
&lt;p&gt;Honor tw.cancel before entering __do_wait(). Complete the request with
-ECANCELED and skip the siginfo copy, since canceled task work may run
without the submitting task&amp;#39;s userspace execution context.&lt;/p&gt;
&lt;p&gt;Keep the existing siginfo handling for normal waitid completion and
explicit cancellation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-81010</guid>
    </item>
  </channel>
</rss>
