<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 09:07:58 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01249</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-01249</link>
      <description>bdu:2026-01249</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-01249</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-54056</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-54056</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-54056</guid>
    </item>
    <item>
      <title>EUVD-2026-312348</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312348</link>
      <description>EUVD-2026-312348</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312348</guid>
    </item>
    <item>
      <title>fkie_cve-2023-54056</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-54056</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2023-54056</guid>
    </item>
    <item>
      <title>GHSA-w8p6-7x4v-892g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w8p6-7x4v-892g</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-w8p6-7x4v-892g</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-54056</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54056</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 136 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kheaders: Use array declaration instead of char 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). This was seen with:   $ cat /sys/kernel/kheaders.tar.xz &amp;gt;&amp;gt; /dev/null   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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 136 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kheaders: Use array declaration instead of char 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). This was seen with:   $ cat /sys/kernel/kheaders.tar.xz &amp;gt;&amp;gt; /dev/null   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://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54056</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</guid>
    </item>
  </channel>
</rss>
