<?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 09:36:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46704 — workqueue: Fix spruious data race in __flush_work()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46704</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;workqueue: Fix spruious data race in __flush_work()&lt;/p&gt;
&lt;p&gt;When flushing a work item for cancellation, __flush_work() knows that it
exclusively owns the work item through its PENDING bit. 134874e2eee9
(&amp;#34;workqueue: Allow cancel_work_sync() and disable_work() from atomic
contexts on BH work items&amp;#34;) added a read of @work-&amp;gt;data to determine whether
to use busy wait for BH work items that are being canceled. While the read
is safe when @from_cancel, @work-&amp;gt;data was read before testing @from_cancel
to simplify code structure:&lt;/p&gt;
&lt;p&gt;data = *work_data_bits(work);
	if (from_cancel &amp;amp;&amp;amp;
	    !WARN_ON_ONCE(data &amp;amp; WORK_STRUCT_PWQ) &amp;amp;&amp;amp; (data &amp;amp; WORK_OFFQ_BH)) {&lt;/p&gt;
&lt;p&gt;While the read data was never used if !@from_cancel, this could trigger
KCSAN data race detection spuriously:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KCSAN: data-race in __flush_work / __flush_work&lt;/p&gt;
&lt;p&gt;write to 0xffff8881223aa3e8 of 8 bytes by task 3998 on cpu 0:
   instrument_write include/linux/instrumented.h:41 [inline]
   ___set_bit include/asm-generic/bitops/instrumented-non-atomic.h:28 [inline]
   insert_wq_barrier kernel/workqueue.c:3790 [inline]
   start_flush_work kernel/workqueue.c:4142 [inline]
   __flush_work+0x30b/0x570 kernel/workqueue.c:4178
   flush_work kernel/workqueue.c:4229 [inline]
   ...&lt;/p&gt;
&lt;p&gt;read to 0xffff8881223aa3e8 of 8 bytes by task 50 on cpu 1:
   __flush_work+0x42a/0x570 kernel/workqueue.c:4188
   flush_work kerne…&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;workqueue: Fix spruious data race in __flush_work()&lt;/p&gt;
&lt;p&gt;When flushing a work item for cancellation, __flush_work() knows that it
exclusively owns the work item through its PENDING bit. 134874e2eee9
(&amp;#34;workqueue: Allow cancel_work_sync() and disable_work() from atomic
contexts on BH work items&amp;#34;) added a read of @work-&amp;gt;data to determine whether
to use busy wait for BH work items that are being canceled. While the read
is safe when @from_cancel, @work-&amp;gt;data was read before testing @from_cancel
to simplify code structure:&lt;/p&gt;
&lt;p&gt;data = *work_data_bits(work);
	if (from_cancel &amp;amp;&amp;amp;
	    !WARN_ON_ONCE(data &amp;amp; WORK_STRUCT_PWQ) &amp;amp;&amp;amp; (data &amp;amp; WORK_OFFQ_BH)) {&lt;/p&gt;
&lt;p&gt;While the read data was never used if !@from_cancel, this could trigger
KCSAN data race detection spuriously:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KCSAN: data-race in __flush_work / __flush_work&lt;/p&gt;
&lt;p&gt;write to 0xffff8881223aa3e8 of 8 bytes by task 3998 on cpu 0:
   instrument_write include/linux/instrumented.h:41 [inline]
   ___set_bit include/asm-generic/bitops/instrumented-non-atomic.h:28 [inline]
   insert_wq_barrier kernel/workqueue.c:3790 [inline]
   start_flush_work kernel/workqueue.c:4142 [inline]
   __flush_work+0x30b/0x570 kernel/workqueue.c:4178
   flush_work kernel/workqueue.c:4229 [inline]
   ...&lt;/p&gt;
&lt;p&gt;read to 0xffff8881223aa3e8 of 8 bytes by task 50 on cpu 1:
   __flush_work+0x42a/0x570 kernel/workqueue.c:4188
   flush_work kerne…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46704</guid>
    </item>
  </channel>
</rss>
