<?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 01:49:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38002 — io_uring/fdinfo: grab ctx-&gt;uring_lock around io_uring_show_fdinfo()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38002</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/fdinfo: grab ctx-&amp;gt;uring_lock around io_uring_show_fdinfo()&lt;/p&gt;
&lt;p&gt;Not everything requires locking in there, which is why the &amp;#39;has_lock&amp;#39;
variable exists. But enough does that it&amp;#39;s a bit unwieldy to manage.
Wrap the whole thing in a -&amp;gt;uring_lock trylock, and just return
with no output if we fail to grab it. The existing trylock() will
already have greatly diminished utility/output for the failure case.&lt;/p&gt;
&lt;p&gt;This fixes an issue with reading the SQE fields, if the ring is being
actively resized at the same time.&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/fdinfo: grab ctx-&amp;gt;uring_lock around io_uring_show_fdinfo()&lt;/p&gt;
&lt;p&gt;Not everything requires locking in there, which is why the &amp;#39;has_lock&amp;#39;
variable exists. But enough does that it&amp;#39;s a bit unwieldy to manage.
Wrap the whole thing in a -&amp;gt;uring_lock trylock, and just return
with no output if we fail to grab it. The existing trylock() will
already have greatly diminished utility/output for the failure case.&lt;/p&gt;
&lt;p&gt;This fixes an issue with reading the SQE fields, if the ring is being
actively resized at the same time.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38002</guid>
    </item>
  </channel>
</rss>
