<?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 21:35:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89587 — ACPI: pfr_update: fix stack buffer overflow in query_capability()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89587</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;ACPI: pfr_update: fix stack buffer overflow in query_capability()&lt;/p&gt;
&lt;p&gt;query_capability() copies four ACPI buffer objects returned by the
firmware _DSM into fixed-size u8[16] fields in struct
pfru_update_cap_info using memcpy with the firmware-supplied length:&lt;/p&gt;
&lt;p&gt;memcpy(&amp;amp;cap_hdr-&amp;gt;code_type,
         elements[CAP_CODE_TYPE_IDX].buffer.pointer,
         elements[CAP_CODE_TYPE_IDX].buffer.length);&lt;/p&gt;
&lt;p&gt;The same pattern repeats for drv_type, platform_id, and oem_id.
If the firmware returns buffer.length &amp;gt; 16 for any of these fields,
memcpy writes past the destination array.&lt;/p&gt;
&lt;p&gt;struct pfru_update_cap_info is stack-allocated in pfru_ioctl().&lt;/p&gt;
&lt;p&gt;Confirmed with KASAN on 7.2-rc6: three stack-out-of-bounds reports
are generated when a DSM returns 64-byte buffers, with writes reaching
44 bytes past the end of cap_hdr&amp;#39;s [64, 156) frame window into
adjacent stack redzones.&lt;/p&gt;
&lt;p&gt;Introduce a helper pointer to out_obj-&amp;gt;package.elements and use it
to validate each buffer length against its destination field size
before copying, returning -EINVAL if the firmware supplies an
oversized buffer.&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;ACPI: pfr_update: fix stack buffer overflow in query_capability()&lt;/p&gt;
&lt;p&gt;query_capability() copies four ACPI buffer objects returned by the
firmware _DSM into fixed-size u8[16] fields in struct
pfru_update_cap_info using memcpy with the firmware-supplied length:&lt;/p&gt;
&lt;p&gt;memcpy(&amp;amp;cap_hdr-&amp;gt;code_type,
         elements[CAP_CODE_TYPE_IDX].buffer.pointer,
         elements[CAP_CODE_TYPE_IDX].buffer.length);&lt;/p&gt;
&lt;p&gt;The same pattern repeats for drv_type, platform_id, and oem_id.
If the firmware returns buffer.length &amp;gt; 16 for any of these fields,
memcpy writes past the destination array.&lt;/p&gt;
&lt;p&gt;struct pfru_update_cap_info is stack-allocated in pfru_ioctl().&lt;/p&gt;
&lt;p&gt;Confirmed with KASAN on 7.2-rc6: three stack-out-of-bounds reports
are generated when a DSM returns 64-byte buffers, with writes reaching
44 bytes past the end of cap_hdr&amp;#39;s [64, 156) frame window into
adjacent stack redzones.&lt;/p&gt;
&lt;p&gt;Introduce a helper pointer to out_obj-&amp;gt;package.elements and use it
to validate each buffer length against its destination field size
before copying, returning -EINVAL if the firmware supplies an
oversized buffer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89587</guid>
    </item>
  </channel>
</rss>
