<?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 21:44:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43401 — cpufreq: intel_pstate: Fix NULL pointer dereference in update_cpu_qos_request()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43401</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;cpufreq: intel_pstate: Fix NULL pointer dereference in update_cpu_qos_request()&lt;/p&gt;
&lt;p&gt;The update_cpu_qos_request() function attempts to initialize the &amp;#39;freq&amp;#39;
variable by dereferencing &amp;#39;cpudata&amp;#39; before verifying if the &amp;#39;policy&amp;#39;
is valid.&lt;/p&gt;
&lt;p&gt;This issue occurs on systems booted with the &amp;#34;nosmt&amp;#34; parameter, where
all_cpu_data[cpu] is NULL for the SMT sibling threads. As a result,
any call to update_qos_requests() will result in a NULL pointer
dereference as the code will attempt to access pstate.turbo_freq using
the NULL cpudata pointer.&lt;/p&gt;
&lt;p&gt;Also, pstate.turbo_freq may be updated by intel_pstate_get_hwp_cap()
after initializing the &amp;#39;freq&amp;#39; variable, so it is better to defer the
&amp;#39;freq&amp;#39; until intel_pstate_get_hwp_cap() has been called.&lt;/p&gt;
&lt;p&gt;Fix this by deferring the &amp;#39;freq&amp;#39; assignment until after the policy and
driver_data have been validated.&lt;/p&gt;
&lt;p&gt;[ rjw: Added one paragraph to the changelog ]&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;cpufreq: intel_pstate: Fix NULL pointer dereference in update_cpu_qos_request()&lt;/p&gt;
&lt;p&gt;The update_cpu_qos_request() function attempts to initialize the &amp;#39;freq&amp;#39;
variable by dereferencing &amp;#39;cpudata&amp;#39; before verifying if the &amp;#39;policy&amp;#39;
is valid.&lt;/p&gt;
&lt;p&gt;This issue occurs on systems booted with the &amp;#34;nosmt&amp;#34; parameter, where
all_cpu_data[cpu] is NULL for the SMT sibling threads. As a result,
any call to update_qos_requests() will result in a NULL pointer
dereference as the code will attempt to access pstate.turbo_freq using
the NULL cpudata pointer.&lt;/p&gt;
&lt;p&gt;Also, pstate.turbo_freq may be updated by intel_pstate_get_hwp_cap()
after initializing the &amp;#39;freq&amp;#39; variable, so it is better to defer the
&amp;#39;freq&amp;#39; until intel_pstate_get_hwp_cap() has been called.&lt;/p&gt;
&lt;p&gt;Fix this by deferring the &amp;#39;freq&amp;#39; assignment until after the policy and
driver_data have been validated.&lt;/p&gt;
&lt;p&gt;[ rjw: Added one paragraph to the changelog ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43401</guid>
    </item>
  </channel>
</rss>
