<?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>Sun, 04 Oct 2026 09:44:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52672 — pipe: wakeup wr_wait after setting max_usage</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52672</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pipe: wakeup wr_wait after setting max_usage&lt;/p&gt;
&lt;p&gt;Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a
regression was introduced that would lock up resized pipes under certain
conditions. See the reproducer in [1].&lt;/p&gt;
&lt;p&gt;The commit resizing the pipe ring size was moved to a different
function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually
raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it
would result in the wakeup never actually triggering pipe_write.&lt;/p&gt;
&lt;p&gt;Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a
watch queue.&lt;/p&gt;
&lt;p&gt;[Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pipe: wakeup wr_wait after setting max_usage&lt;/p&gt;
&lt;p&gt;Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a
regression was introduced that would lock up resized pipes under certain
conditions. See the reproducer in [1].&lt;/p&gt;
&lt;p&gt;The commit resizing the pipe ring size was moved to a different
function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually
raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it
would result in the wakeup never actually triggering pipe_write.&lt;/p&gt;
&lt;p&gt;Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a
watch queue.&lt;/p&gt;
&lt;p&gt;[Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52672</guid>
    </item>
  </channel>
</rss>
