<?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 18:04:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23452 — PM: runtime: Fix a race condition related to device removal</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23452</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PM: runtime: Fix a race condition related to device removal&lt;/p&gt;
&lt;p&gt;The following code in pm_runtime_work() may dereference the dev-&amp;gt;parent
pointer after the parent device has been freed:&lt;/p&gt;
&lt;p&gt;/* Maybe the parent is now able to suspend. */
	if (parent &amp;amp;&amp;amp; !parent-&amp;gt;power.ignore_children) {
		spin_unlock(&amp;amp;dev-&amp;gt;power.lock);&lt;/p&gt;
&lt;p&gt;spin_lock(&amp;amp;parent-&amp;gt;power.lock);
		rpm_idle(parent, RPM_ASYNC);
		spin_unlock(&amp;amp;parent-&amp;gt;power.lock);&lt;/p&gt;
&lt;p&gt;spin_lock(&amp;amp;dev-&amp;gt;power.lock);
	}&lt;/p&gt;
&lt;p&gt;Fix this by inserting a flush_work() call in pm_runtime_remove().&lt;/p&gt;
&lt;p&gt;Without this patch blktest block/001 triggers the following complaint
sporadically:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in lock_acquire+0x70/0x160
Read of size 1 at addr ffff88812bef7198 by task kworker/u553:1/3081
Workqueue: pm pm_runtime_work
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0x61/0x80
 print_address_description.constprop.0+0x8b/0x310
 print_report+0xfd/0x1d7
 kasan_report+0xd8/0x1d0
 __kasan_check_byte+0x42/0x60
 lock_acquire.part.0+0x38/0x230
 lock_acquire+0x70/0x160
 _raw_spin_lock+0x36/0x50
 rpm_suspend+0xc6a/0xfe0
 rpm_idle+0x578/0x770
 pm_runtime_work+0xee/0x120
 process_one_work+0xde3/0x1410
 worker_thread+0x5eb/0xfe0
 kthread+0x37b/0x480
 ret_from_fork+0x6cb/0x920
 ret_from_fork_asm+0x11/0x20
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Allocated by task 4314:
 kasan_save_stack+0x2a/0x50
 kasan_save_track+0x18/0x40
 kasan_save_alloc_info+0x3d/0x50
 __kasan_kmalloc+0xa0/0xb0
 __kmalloc_noprof+0x311/0x990
 scsi_alloc_target+0x1…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PM: runtime: Fix a race condition related to device removal&lt;/p&gt;
&lt;p&gt;The following code in pm_runtime_work() may dereference the dev-&amp;gt;parent
pointer after the parent device has been freed:&lt;/p&gt;
&lt;p&gt;/* Maybe the parent is now able to suspend. */
	if (parent &amp;amp;&amp;amp; !parent-&amp;gt;power.ignore_children) {
		spin_unlock(&amp;amp;dev-&amp;gt;power.lock);&lt;/p&gt;
&lt;p&gt;spin_lock(&amp;amp;parent-&amp;gt;power.lock);
		rpm_idle(parent, RPM_ASYNC);
		spin_unlock(&amp;amp;parent-&amp;gt;power.lock);&lt;/p&gt;
&lt;p&gt;spin_lock(&amp;amp;dev-&amp;gt;power.lock);
	}&lt;/p&gt;
&lt;p&gt;Fix this by inserting a flush_work() call in pm_runtime_remove().&lt;/p&gt;
&lt;p&gt;Without this patch blktest block/001 triggers the following complaint
sporadically:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in lock_acquire+0x70/0x160
Read of size 1 at addr ffff88812bef7198 by task kworker/u553:1/3081
Workqueue: pm pm_runtime_work
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0x61/0x80
 print_address_description.constprop.0+0x8b/0x310
 print_report+0xfd/0x1d7
 kasan_report+0xd8/0x1d0
 __kasan_check_byte+0x42/0x60
 lock_acquire.part.0+0x38/0x230
 lock_acquire+0x70/0x160
 _raw_spin_lock+0x36/0x50
 rpm_suspend+0xc6a/0xfe0
 rpm_idle+0x578/0x770
 pm_runtime_work+0xee/0x120
 process_one_work+0xde3/0x1410
 worker_thread+0x5eb/0xfe0
 kthread+0x37b/0x480
 ret_from_fork+0x6cb/0x920
 ret_from_fork_asm+0x11/0x20
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Allocated by task 4314:
 kasan_save_stack+0x2a/0x50
 kasan_save_track+0x18/0x40
 kasan_save_alloc_info+0x3d/0x50
 __kasan_kmalloc+0xa0/0xb0
 __kmalloc_noprof+0x311/0x990
 scsi_alloc_target+0x1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23452</guid>
    </item>
  </channel>
</rss>
