<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T20:52:54.844953+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-99800</id>
    <title>CVE-2026-99800 — io_uring: free the task context after a grace period</title>
    <updated>2026-11-20T20:52:54.846493+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>io_uring: free the task context after a grace period</p>
<p>A task other than the owner can free a request, io_ring_exit_work()
running the local task_work of a DEFER_TASKRUN ring for example, or
io_do_iopoll() reaping completions. io_put_task() then takes the else
branch:</p>
<p>percpu_counter_sub(&amp;tctx-&gt;inflight, 1);
    if (unlikely(atomic_read(&amp;tctx-&gt;in_cancel)))
            wake_up(&amp;tctx-&gt;wait);
    put_task_struct(tctx-&gt;task);</p>
<p>The first line is what lets the owner leave io_uring_cancel_generic(),
and on exec it frees the tctx right after. Nothing holds that off for
the remaining three lines, the task reference only covers a tctx freed
along with the task_struct. It used to work out because
io_uring_del_tctx_node() took the uring_lock that the freeing side holds
across io_put_task(), until that moved to tctx_lock.</p>
<p>Free the tctx with kfree_rcu(), and enter an RCU read section in
io_put_task() before the count is dropped.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99800"/>
  </entry>
</feed>
