<?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>Fri, 02 Oct 2026 15:59:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39904 — arm64: kexec: initialize kexec_buf struct in load_other_segments()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39904</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;arm64: kexec: initialize kexec_buf struct in load_other_segments()&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;kexec: Fix invalid field access&amp;#34;.&lt;/p&gt;
&lt;p&gt;The kexec_buf structure was previously declared without initialization. 
commit bf454ec31add (&amp;#34;kexec_file: allow to place kexec_buf randomly&amp;#34;)
added a field that is always read but not consistently populated by all
architectures.  This un-initialized field will contain garbage.&lt;/p&gt;
&lt;p&gt;This is also triggering a UBSAN warning when the uninitialized data was
accessed:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
	UBSAN: invalid-load in ./include/linux/kexec.h:210:10
	load of value 252 is not a valid value for type &amp;#39;_Bool&amp;#39;&lt;/p&gt;
&lt;p&gt;Zero-initializing kexec_buf at declaration ensures all fields are cleanly
set, preventing future instances of uninitialized memory being used.&lt;/p&gt;
&lt;p&gt;An initial fix was already landed for arm64[0], and this patchset fixes
the problem on the remaining arm64 code and on riscv, as raised by Mark.&lt;/p&gt;
&lt;p&gt;Discussions about this problem could be found at[1][2].&lt;/p&gt;
&lt;p&gt;This patch (of 3):&lt;/p&gt;
&lt;p&gt;The kexec_buf structure was previously declared without initialization.
commit bf454ec31add (&amp;#34;kexec_file: allow to place kexec_buf randomly&amp;#34;)
added a field that is always read but not consistently populated by all
architectures. This un-initialized field will contain garbage.&lt;/p&gt;
&lt;p&gt;This is also triggering a UBSAN warning when the uninitialized data was
accessed:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
	UBSAN: invalid-load in ./includ…&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;arm64: kexec: initialize kexec_buf struct in load_other_segments()&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;kexec: Fix invalid field access&amp;#34;.&lt;/p&gt;
&lt;p&gt;The kexec_buf structure was previously declared without initialization. 
commit bf454ec31add (&amp;#34;kexec_file: allow to place kexec_buf randomly&amp;#34;)
added a field that is always read but not consistently populated by all
architectures.  This un-initialized field will contain garbage.&lt;/p&gt;
&lt;p&gt;This is also triggering a UBSAN warning when the uninitialized data was
accessed:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
	UBSAN: invalid-load in ./include/linux/kexec.h:210:10
	load of value 252 is not a valid value for type &amp;#39;_Bool&amp;#39;&lt;/p&gt;
&lt;p&gt;Zero-initializing kexec_buf at declaration ensures all fields are cleanly
set, preventing future instances of uninitialized memory being used.&lt;/p&gt;
&lt;p&gt;An initial fix was already landed for arm64[0], and this patchset fixes
the problem on the remaining arm64 code and on riscv, as raised by Mark.&lt;/p&gt;
&lt;p&gt;Discussions about this problem could be found at[1][2].&lt;/p&gt;
&lt;p&gt;This patch (of 3):&lt;/p&gt;
&lt;p&gt;The kexec_buf structure was previously declared without initialization.
commit bf454ec31add (&amp;#34;kexec_file: allow to place kexec_buf randomly&amp;#34;)
added a field that is always read but not consistently populated by all
architectures. This un-initialized field will contain garbage.&lt;/p&gt;
&lt;p&gt;This is also triggering a UBSAN warning when the uninitialized data was
accessed:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
	UBSAN: invalid-load in ./includ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39904</guid>
    </item>
  </channel>
</rss>
