<?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>Mon, 05 Oct 2026 06:28:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52895 — io_uring/poll: don't reissue in case of poll race on multishot request</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52895</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/poll: don&amp;#39;t reissue in case of poll race on multishot request&lt;/p&gt;
&lt;p&gt;A previous commit fixed a poll race that can occur, but it&amp;#39;s only
applicable for multishot requests. For a multishot request, we can safely
ignore a spurious wakeup, as we never leave the waitqueue to begin with.&lt;/p&gt;
&lt;p&gt;A blunt reissue of a multishot armed request can cause us to leak a
buffer, if they are ring provided. While this seems like a bug in itself,
it&amp;#39;s not really defined behavior to reissue a multishot request directly.
It&amp;#39;s less efficient to do so as well, and not required to rearm anything
like it is for singleshot poll requests.&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/poll: don&amp;#39;t reissue in case of poll race on multishot request&lt;/p&gt;
&lt;p&gt;A previous commit fixed a poll race that can occur, but it&amp;#39;s only
applicable for multishot requests. For a multishot request, we can safely
ignore a spurious wakeup, as we never leave the waitqueue to begin with.&lt;/p&gt;
&lt;p&gt;A blunt reissue of a multishot armed request can cause us to leak a
buffer, if they are ring provided. While this seems like a bug in itself,
it&amp;#39;s not really defined behavior to reissue a multishot request directly.
It&amp;#39;s less efficient to do so as well, and not required to rearm anything
like it is for singleshot poll requests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52895</guid>
    </item>
  </channel>
</rss>
