<?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>Sat, 03 Oct 2026 19:25:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40130 — scsi: ufs: core: Fix data race in CPU latency PM QoS request handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40130</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 data race in CPU latency PM QoS request handling&lt;/p&gt;
&lt;p&gt;The cpu_latency_qos_add/remove/update_request interfaces lack internal
synchronization by design, requiring the caller to ensure thread safety.
The current implementation relies on the &amp;#39;pm_qos_enabled&amp;#39; flag, which is
insufficient to prevent concurrent access and cannot serve as a proper
synchronization mechanism. This has led to data races and list
corruption issues.&lt;/p&gt;
&lt;p&gt;A typical race condition call trace is:&lt;/p&gt;
&lt;p&gt;[Thread A]
ufshcd_pm_qos_exit()
  --&amp;gt; cpu_latency_qos_remove_request()
    --&amp;gt; cpu_latency_qos_apply();
      --&amp;gt; pm_qos_update_target()
        --&amp;gt; plist_del              &amp;lt;--(1) delete plist node
    --&amp;gt; memset(req, 0, sizeof(*req));
  --&amp;gt; hba-&amp;gt;pm_qos_enabled = false;&lt;/p&gt;
&lt;p&gt;[Thread B]
ufshcd_devfreq_target
  --&amp;gt; ufshcd_devfreq_scale
    --&amp;gt; ufshcd_scale_clks
      --&amp;gt; ufshcd_pm_qos_update     &amp;lt;--(2) pm_qos_enabled is true
        --&amp;gt; cpu_latency_qos_update_request
          --&amp;gt; pm_qos_update_target
            --&amp;gt; plist_del          &amp;lt;--(3) plist node use-after-free&lt;/p&gt;
&lt;p&gt;Introduces a dedicated mutex to serialize PM QoS operations, preventing
data races and ensuring safe access to PM QoS resources, including sysfs
interface reads.&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 data race in CPU latency PM QoS request handling&lt;/p&gt;
&lt;p&gt;The cpu_latency_qos_add/remove/update_request interfaces lack internal
synchronization by design, requiring the caller to ensure thread safety.
The current implementation relies on the &amp;#39;pm_qos_enabled&amp;#39; flag, which is
insufficient to prevent concurrent access and cannot serve as a proper
synchronization mechanism. This has led to data races and list
corruption issues.&lt;/p&gt;
&lt;p&gt;A typical race condition call trace is:&lt;/p&gt;
&lt;p&gt;[Thread A]
ufshcd_pm_qos_exit()
  --&amp;gt; cpu_latency_qos_remove_request()
    --&amp;gt; cpu_latency_qos_apply();
      --&amp;gt; pm_qos_update_target()
        --&amp;gt; plist_del              &amp;lt;--(1) delete plist node
    --&amp;gt; memset(req, 0, sizeof(*req));
  --&amp;gt; hba-&amp;gt;pm_qos_enabled = false;&lt;/p&gt;
&lt;p&gt;[Thread B]
ufshcd_devfreq_target
  --&amp;gt; ufshcd_devfreq_scale
    --&amp;gt; ufshcd_scale_clks
      --&amp;gt; ufshcd_pm_qos_update     &amp;lt;--(2) pm_qos_enabled is true
        --&amp;gt; cpu_latency_qos_update_request
          --&amp;gt; pm_qos_update_target
            --&amp;gt; plist_del          &amp;lt;--(3) plist node use-after-free&lt;/p&gt;
&lt;p&gt;Introduces a dedicated mutex to serialize PM QoS operations, preventing
data races and ensuring safe access to PM QoS resources, including sysfs
interface reads.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40130</guid>
    </item>
  </channel>
</rss>
