arm64: RSI: fix field-spanning write warning in attestation token init
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: arm64: RSI: fix field-spanning write warning in attestation token init The challenge is passed in registers a1 through a8. However, copying to ®s.a1 makes FORTIFY treat the destination as the single a1 field, resulting in a field-spanning write warning. [1] 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. [1] memcpy: detected field-spanning write (size 64) of single field "®s.a1" 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
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b880a80011f56880f32bde47fc6af313359f926b · fixed in e505092cb200d430d5b8d8d3e926d45f29474ba3; From b880a80011f56880f32bde47fc6af313359f926b · fixed in d29a8ee271da17b5e32d7a76a9c78d43f66447ca; From b880a80011f56880f32bde47fc6af313359f926b · fixed in 221049874b6a78c7d87bc826581b0695cd338e2b
- Linux Linux
6.13
- KernelLinux
From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6