<?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 20:37:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52836 — locking/ww_mutex/test: Fix potential workqueue corruption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52836</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;locking/ww_mutex/test: Fix potential workqueue corruption&lt;/p&gt;
&lt;p&gt;In some cases running with the test-ww_mutex code, I was seeing
odd behavior where sometimes it seemed flush_workqueue was
returning before all the work threads were finished.&lt;/p&gt;
&lt;p&gt;Often this would cause strange crashes as the mutexes would be
freed while they were being used.&lt;/p&gt;
&lt;p&gt;Looking at the code, there is a lifetime problem as the
controlling thread that spawns the work allocates the
&amp;#34;struct stress&amp;#34; structures that are passed to the workqueue
threads. Then when the workqueue threads are finished,
they free the stress struct that was passed to them.&lt;/p&gt;
&lt;p&gt;Unfortunately the workqueue work_struct node is in the stress
struct. Which means the work_struct is freed before the work
thread returns and while flush_workqueue is waiting.&lt;/p&gt;
&lt;p&gt;It seems like a better idea to have the controlling thread
both allocate and free the stress structures, so that we can
be sure we don&amp;#39;t corrupt the workqueue by freeing the structure
prematurely.&lt;/p&gt;
&lt;p&gt;So this patch reworks the test to do so, and with this change
I no longer see the early flush_workqueue returns.&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;locking/ww_mutex/test: Fix potential workqueue corruption&lt;/p&gt;
&lt;p&gt;In some cases running with the test-ww_mutex code, I was seeing
odd behavior where sometimes it seemed flush_workqueue was
returning before all the work threads were finished.&lt;/p&gt;
&lt;p&gt;Often this would cause strange crashes as the mutexes would be
freed while they were being used.&lt;/p&gt;
&lt;p&gt;Looking at the code, there is a lifetime problem as the
controlling thread that spawns the work allocates the
&amp;#34;struct stress&amp;#34; structures that are passed to the workqueue
threads. Then when the workqueue threads are finished,
they free the stress struct that was passed to them.&lt;/p&gt;
&lt;p&gt;Unfortunately the workqueue work_struct node is in the stress
struct. Which means the work_struct is freed before the work
thread returns and while flush_workqueue is waiting.&lt;/p&gt;
&lt;p&gt;It seems like a better idea to have the controlling thread
both allocate and free the stress structures, so that we can
be sure we don&amp;#39;t corrupt the workqueue by freeing the structure
prematurely.&lt;/p&gt;
&lt;p&gt;So this patch reworks the test to do so, and with this change
I no longer see the early flush_workqueue returns.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52836</guid>
    </item>
  </channel>
</rss>
