<?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 14:33:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93266 — arm64: RSI: fix field-spanning write warning in attestation token init</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93266</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: RSI: fix field-spanning write warning in attestation token init&lt;/p&gt;
&lt;p&gt;The challenge is passed in registers a1 through a8. However, copying to
&amp;amp;regs.a1 makes FORTIFY treat the destination as the single a1 field,
resulting in a field-spanning write warning. [1]&lt;/p&gt;
&lt;p&gt;Overlay the SMCCC register structure with an RSI-specific argument
layout and copy the challenge into an explicit 64-byte array. This keeps
the existing a1-a8 argument encoding while giving the copy a correctly
sized destination object.&lt;/p&gt;
&lt;p&gt;[1]
memcpy: detected field-spanning write (size 64) of single field &amp;#34;&amp;amp;regs.a1&amp;#34; at ./arch/arm64/include/asm/rsi_cmds.h:119 (size 8)
WARNING: ./arch/arm64/include/asm/rsi_cmds.h:119 at rsi_attestation_token_init+0xdc/0xf8 [arm_cca_guest], CPU#0: cat/3314&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: RSI: fix field-spanning write warning in attestation token init&lt;/p&gt;
&lt;p&gt;The challenge is passed in registers a1 through a8. However, copying to
&amp;amp;regs.a1 makes FORTIFY treat the destination as the single a1 field,
resulting in a field-spanning write warning. [1]&lt;/p&gt;
&lt;p&gt;Overlay the SMCCC register structure with an RSI-specific argument
layout and copy the challenge into an explicit 64-byte array. This keeps
the existing a1-a8 argument encoding while giving the copy a correctly
sized destination object.&lt;/p&gt;
&lt;p&gt;[1]
memcpy: detected field-spanning write (size 64) of single field &amp;#34;&amp;amp;regs.a1&amp;#34; at ./arch/arm64/include/asm/rsi_cmds.h:119 (size 8)
WARNING: ./arch/arm64/include/asm/rsi_cmds.h:119 at rsi_attestation_token_init+0xdc/0xf8 [arm_cca_guest], CPU#0: cat/3314&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93266</guid>
    </item>
  </channel>
</rss>
