<?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>Thu, 01 Oct 2026 11:08:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49436 — powerpc/papr_scm: Fix leaking nvdimm_events_map elements</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49436</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;powerpc/papr_scm: Fix leaking nvdimm_events_map elements&lt;/p&gt;
&lt;p&gt;Right now &amp;#39;char *&amp;#39; elements allocated for individual &amp;#39;stat_id&amp;#39; in
&amp;#39;papr_scm_priv.nvdimm_events_map[]&amp;#39; during papr_scm_pmu_check_events(), get
leaked in papr_scm_remove() and papr_scm_pmu_register(),
papr_scm_pmu_check_events() error paths.&lt;/p&gt;
&lt;p&gt;Also individual &amp;#39;stat_id&amp;#39; arent NULL terminated &amp;#39;char *&amp;#39; instead they are fixed
8-byte sized identifiers. However papr_scm_pmu_register() assumes it to be a
NULL terminated &amp;#39;char *&amp;#39; and at other places it assumes it to be a
&amp;#39;papr_scm_perf_stat.stat_id&amp;#39; sized string which is 8-byes in size.&lt;/p&gt;
&lt;p&gt;Fix this by allocating the memory for papr_scm_priv.nvdimm_events_map to also
include space for &amp;#39;stat_id&amp;#39; entries. This is possible since number of available
events/stat_ids are known upfront. This saves some memory and one extra level of
indirection from &amp;#39;nvdimm_events_map&amp;#39; to &amp;#39;stat_id&amp;#39;. Also rest of the code
can continue to call &amp;#39;kfree(papr_scm_priv.nvdimm_events_map)&amp;#39; without needing to
iterate over the array and free up individual elements.&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;powerpc/papr_scm: Fix leaking nvdimm_events_map elements&lt;/p&gt;
&lt;p&gt;Right now &amp;#39;char *&amp;#39; elements allocated for individual &amp;#39;stat_id&amp;#39; in
&amp;#39;papr_scm_priv.nvdimm_events_map[]&amp;#39; during papr_scm_pmu_check_events(), get
leaked in papr_scm_remove() and papr_scm_pmu_register(),
papr_scm_pmu_check_events() error paths.&lt;/p&gt;
&lt;p&gt;Also individual &amp;#39;stat_id&amp;#39; arent NULL terminated &amp;#39;char *&amp;#39; instead they are fixed
8-byte sized identifiers. However papr_scm_pmu_register() assumes it to be a
NULL terminated &amp;#39;char *&amp;#39; and at other places it assumes it to be a
&amp;#39;papr_scm_perf_stat.stat_id&amp;#39; sized string which is 8-byes in size.&lt;/p&gt;
&lt;p&gt;Fix this by allocating the memory for papr_scm_priv.nvdimm_events_map to also
include space for &amp;#39;stat_id&amp;#39; entries. This is possible since number of available
events/stat_ids are known upfront. This saves some memory and one extra level of
indirection from &amp;#39;nvdimm_events_map&amp;#39; to &amp;#39;stat_id&amp;#39;. Also rest of the code
can continue to call &amp;#39;kfree(papr_scm_priv.nvdimm_events_map)&amp;#39; without needing to
iterate over the array and free up individual elements.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49436</guid>
    </item>
  </channel>
</rss>
