<?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 05:39:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90178 — hwmon: (coretemp) Fix core_data leak on CPUs without PTS</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90178</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;hwmon: (coretemp) Fix core_data leak on CPUs without PTS&lt;/p&gt;
&lt;p&gt;pdata-&amp;gt;core_data is allocated in init_temp_data() when the first core
temp_data of a package is created, but it is only released from
destroy_temp_data(), and only in the branch that handles the package
temp_data.&lt;/p&gt;
&lt;p&gt;Package temp_data is created solely when the CPU supports
X86_FEATURE_PTS. On a CPU without it, coretemp_cpu_online() never calls
coretemp_add_core() with pkg_flag set, so pdata-&amp;gt;pkg_data stays NULL.
coretemp_cpu_offline() then skips the removal of the package interface,
destroy_temp_data() is never called for package data, and the array is
still allocated when coretemp_device_remove() frees the platform data
that pointed at it.&lt;/p&gt;
&lt;p&gt;Release the array in coretemp_device_remove(). destroy_temp_data() sets
pdata-&amp;gt;core_data to NULL when it frees it, so the added kfree() is a
no-op on CPUs that do have PTS.&lt;/p&gt;
&lt;p&gt;Tested on an Intel Core i5-1135G7. The driver was instrumented to log
every allocation and release of pdata-&amp;gt;core_data, and the PTS check in
coretemp_cpu_online() was patched out to emulate a CPU without package
thermal support. Without this change the array was allocated and never
released, and coretemp_device_remove() still saw a non-NULL pointer.
With it the array is released and the pointer accounting balances. On an
unmodified build the release still happens via the package temp_data and
the added kfree() sees NULL, with no slab warnings…&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;hwmon: (coretemp) Fix core_data leak on CPUs without PTS&lt;/p&gt;
&lt;p&gt;pdata-&amp;gt;core_data is allocated in init_temp_data() when the first core
temp_data of a package is created, but it is only released from
destroy_temp_data(), and only in the branch that handles the package
temp_data.&lt;/p&gt;
&lt;p&gt;Package temp_data is created solely when the CPU supports
X86_FEATURE_PTS. On a CPU without it, coretemp_cpu_online() never calls
coretemp_add_core() with pkg_flag set, so pdata-&amp;gt;pkg_data stays NULL.
coretemp_cpu_offline() then skips the removal of the package interface,
destroy_temp_data() is never called for package data, and the array is
still allocated when coretemp_device_remove() frees the platform data
that pointed at it.&lt;/p&gt;
&lt;p&gt;Release the array in coretemp_device_remove(). destroy_temp_data() sets
pdata-&amp;gt;core_data to NULL when it frees it, so the added kfree() is a
no-op on CPUs that do have PTS.&lt;/p&gt;
&lt;p&gt;Tested on an Intel Core i5-1135G7. The driver was instrumented to log
every allocation and release of pdata-&amp;gt;core_data, and the PTS check in
coretemp_cpu_online() was patched out to emulate a CPU without package
thermal support. Without this change the array was allocated and never
released, and coretemp_device_remove() still saw a non-NULL pointer.
With it the array is released and the pointer accounting balances. On an
unmodified build the release still happens via the package temp_data and
the added kfree() sees NULL, with no slab warnings…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90178</guid>
    </item>
  </channel>
</rss>
