<?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 14:36:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-44953 — scsi: ufs: core: Fix deadlock during RTC update</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-44953</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;scsi: ufs: core: Fix deadlock during RTC update&lt;/p&gt;
&lt;p&gt;There is a deadlock when runtime suspend waits for the flush of RTC work,
and the RTC work calls ufshcd_rpm_get_sync() to wait for runtime resume.&lt;/p&gt;
&lt;p&gt;Here is deadlock backtrace:&lt;/p&gt;
&lt;p&gt;kworker/0:1     D 4892.876354 10 10971 4859 0x4208060 0x8 10 0 120 670730152367
ptr            f0ffff80c2e40000 0 1 0x00000001 0x000000ff 0x000000ff 0x000000ff
&amp;lt;ffffffee5e71ddb0&amp;gt; __switch_to+0x1a8/0x2d4
&amp;lt;ffffffee5e71e604&amp;gt; __schedule+0x684/0xa98
&amp;lt;ffffffee5e71ea60&amp;gt; schedule+0x48/0xc8
&amp;lt;ffffffee5e725f78&amp;gt; schedule_timeout+0x48/0x170
&amp;lt;ffffffee5e71fb74&amp;gt; do_wait_for_common+0x108/0x1b0
&amp;lt;ffffffee5e71efe0&amp;gt; wait_for_completion+0x44/0x60
&amp;lt;ffffffee5d6de968&amp;gt; __flush_work+0x39c/0x424
&amp;lt;ffffffee5d6decc0&amp;gt; __cancel_work_sync+0xd8/0x208
&amp;lt;ffffffee5d6dee2c&amp;gt; cancel_delayed_work_sync+0x14/0x28
&amp;lt;ffffffee5e2551b8&amp;gt; __ufshcd_wl_suspend+0x19c/0x480
&amp;lt;ffffffee5e255fb8&amp;gt; ufshcd_wl_runtime_suspend+0x3c/0x1d4
&amp;lt;ffffffee5dffd80c&amp;gt; scsi_runtime_suspend+0x78/0xc8
&amp;lt;ffffffee5df93580&amp;gt; __rpm_callback+0x94/0x3e0
&amp;lt;ffffffee5df90b0c&amp;gt; rpm_suspend+0x2d4/0x65c
&amp;lt;ffffffee5df91448&amp;gt; __pm_runtime_suspend+0x80/0x114
&amp;lt;ffffffee5dffd95c&amp;gt; scsi_runtime_idle+0x38/0x6c
&amp;lt;ffffffee5df912f4&amp;gt; rpm_idle+0x264/0x338
&amp;lt;ffffffee5df90f14&amp;gt; __pm_runtime_idle+0x80/0x110
&amp;lt;ffffffee5e24ce44&amp;gt; ufshcd_rtc_work+0x128/0x1e4
&amp;lt;ffffffee5d6e3a40&amp;gt; process_one_work+0x26c/0x650
&amp;lt;ffffffee5d6e65c8&amp;gt; worker_thread+0x260/0x3d8
&amp;lt;ffffffee5d6edec8&amp;gt; kthread+0x110/0x134
&amp;lt;ffffffee5d616b18&amp;gt;…&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;scsi: ufs: core: Fix deadlock during RTC update&lt;/p&gt;
&lt;p&gt;There is a deadlock when runtime suspend waits for the flush of RTC work,
and the RTC work calls ufshcd_rpm_get_sync() to wait for runtime resume.&lt;/p&gt;
&lt;p&gt;Here is deadlock backtrace:&lt;/p&gt;
&lt;p&gt;kworker/0:1     D 4892.876354 10 10971 4859 0x4208060 0x8 10 0 120 670730152367
ptr            f0ffff80c2e40000 0 1 0x00000001 0x000000ff 0x000000ff 0x000000ff
&amp;lt;ffffffee5e71ddb0&amp;gt; __switch_to+0x1a8/0x2d4
&amp;lt;ffffffee5e71e604&amp;gt; __schedule+0x684/0xa98
&amp;lt;ffffffee5e71ea60&amp;gt; schedule+0x48/0xc8
&amp;lt;ffffffee5e725f78&amp;gt; schedule_timeout+0x48/0x170
&amp;lt;ffffffee5e71fb74&amp;gt; do_wait_for_common+0x108/0x1b0
&amp;lt;ffffffee5e71efe0&amp;gt; wait_for_completion+0x44/0x60
&amp;lt;ffffffee5d6de968&amp;gt; __flush_work+0x39c/0x424
&amp;lt;ffffffee5d6decc0&amp;gt; __cancel_work_sync+0xd8/0x208
&amp;lt;ffffffee5d6dee2c&amp;gt; cancel_delayed_work_sync+0x14/0x28
&amp;lt;ffffffee5e2551b8&amp;gt; __ufshcd_wl_suspend+0x19c/0x480
&amp;lt;ffffffee5e255fb8&amp;gt; ufshcd_wl_runtime_suspend+0x3c/0x1d4
&amp;lt;ffffffee5dffd80c&amp;gt; scsi_runtime_suspend+0x78/0xc8
&amp;lt;ffffffee5df93580&amp;gt; __rpm_callback+0x94/0x3e0
&amp;lt;ffffffee5df90b0c&amp;gt; rpm_suspend+0x2d4/0x65c
&amp;lt;ffffffee5df91448&amp;gt; __pm_runtime_suspend+0x80/0x114
&amp;lt;ffffffee5dffd95c&amp;gt; scsi_runtime_idle+0x38/0x6c
&amp;lt;ffffffee5df912f4&amp;gt; rpm_idle+0x264/0x338
&amp;lt;ffffffee5df90f14&amp;gt; __pm_runtime_idle+0x80/0x110
&amp;lt;ffffffee5e24ce44&amp;gt; ufshcd_rtc_work+0x128/0x1e4
&amp;lt;ffffffee5d6e3a40&amp;gt; process_one_work+0x26c/0x650
&amp;lt;ffffffee5d6e65c8&amp;gt; worker_thread+0x260/0x3d8
&amp;lt;ffffffee5d6edec8&amp;gt; kthread+0x110/0x134
&amp;lt;ffffffee5d616b18&amp;gt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-44953</guid>
    </item>
  </channel>
</rss>
