<?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 07:21:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54056 — kheaders: Use array declaration instead of char</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54056</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;kheaders: Use array declaration instead of char&lt;/p&gt;
&lt;p&gt;Under CONFIG_FORTIFY_SOURCE, memcpy() will check the size of destination
and source buffers. Defining kernel_headers_data as &amp;#34;char&amp;#34; would trip
this check. Since these addresses are treated as byte arrays, define
them as arrays (as done everywhere else).&lt;/p&gt;
&lt;p&gt;This was seen with:&lt;/p&gt;
&lt;p&gt;$ cat /sys/kernel/kheaders.tar.xz &amp;gt;&amp;gt; /dev/null&lt;/p&gt;
&lt;p&gt;detected buffer overflow in memcpy
  kernel BUG at lib/string_helpers.c:1027!
  ...
  RIP: 0010:fortify_panic+0xf/0x20
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   ikheaders_read+0x45/0x50 [kheaders]
   kernfs_fop_read_iter+0x1a4/0x2f0
  ...&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;kheaders: Use array declaration instead of char&lt;/p&gt;
&lt;p&gt;Under CONFIG_FORTIFY_SOURCE, memcpy() will check the size of destination
and source buffers. Defining kernel_headers_data as &amp;#34;char&amp;#34; would trip
this check. Since these addresses are treated as byte arrays, define
them as arrays (as done everywhere else).&lt;/p&gt;
&lt;p&gt;This was seen with:&lt;/p&gt;
&lt;p&gt;$ cat /sys/kernel/kheaders.tar.xz &amp;gt;&amp;gt; /dev/null&lt;/p&gt;
&lt;p&gt;detected buffer overflow in memcpy
  kernel BUG at lib/string_helpers.c:1027!
  ...
  RIP: 0010:fortify_panic+0xf/0x20
  [...]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   ikheaders_read+0x45/0x50 [kheaders]
   kernfs_fop_read_iter+0x1a4/0x2f0
  ...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54056</guid>
    </item>
  </channel>
</rss>
