CVE-2023-53713 Details
Description
In the Linux kernel, the following vulnerability has been resolved: arm64: sme: Use STR P to clear FFR context field in streaming SVE mode The FFR is a predicate register which can vary between 16 and 256 bits in size depending upon the configured vector length. When saving the SVE state in streaming SVE mode, the FFR register is inaccessible and so commit 9f5848665788 ("arm64/sve: Make access to FFR optional") simply clears the FFR field of the in-memory context structure. Unfortunately, it achieves this using an unconditional 8-byte store and so if the SME vector length is anything other than 64 bytes in size we will either fail to clear the entire field or, worse, we will corrupt memory immediately following the structure. This has led to intermittent kfence splats in CI [1] and can trigger kmalloc Redzone corruption messages when running the 'fp-stress' kselftest: | ============================================================================= | BUG kmalloc-1k (Not tainted): kmalloc Redzone overwritten | ----------------------------------------------------------------------------- | | 0xffff000809bf1e22-0xffff000809bf1e27 @offset=7714. First byte 0x0 instead of 0xcc | Allocated in do_sme_acc+0x9c/0x220 age=2613 cpu=1 pid=531 | __kmalloc+0x8c/0xcc | do_sme_acc+0x9c/0x220 | ... Replace the 8-byte store with a store of a predicate register which has been zero-initialised with PFALSE, ensuring that the entire field is cleared in memory. [1] https://lore.kernel.org/r/CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com
A vulnerability in the Linux kernel's handling of the FFR predicate register during the saving of SVE state in streaming SVE mode has been identified. The issue arises because the FFR register, which can range from 16 to 256 bits depending on the vector length, is inaccessible in this mode. As a result, the kernel attempts to clear the FFR field in the in-memory context structure using an unconditional 8-byte store. This approach is flawed, as it can either fail to clear the entire field or, in cases where the SME vector length exceeds 64 bytes, corrupt memory immediately following the structure. This vulnerability has led to intermittent memory corruption errors in kernel self-tests, particularly when running the 'fp-stress' kselftest, which triggers kmalloc Redzone corruption messages.
The vulnerability has been addressed in the Linux kernel. Users should upgrade to the latest version where this issue has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 22, 2025CISA-ADP
Assessed Oct 15, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1403a899153a12d93fd510e463fd6d0eafba4336 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/8769a62faacbbb6cac5e35d9047ce445183d4e9f | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/893b24181b4c4bf1fa2841b1ed192e5413a97cb1 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/97669214944e80d3756657c21c4f286f3da6a423 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 28, 2026 | CVE Translated | [email protected] |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | CISA-ADP |
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 22, 2025 | New CVE Received | kernel.org |
Volerion