CVE-2023-53713
BaseFortify
Publication date: 2025-10-22
Last updated on: 2025-10-22
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is in the Linux kernel's arm64 architecture related to the SME (Scalable Matrix Extension) and streaming SVE (Scalable Vector Extension) mode. The issue arises because the FFR (First Fault Register), a predicate register whose size varies depending on the vector length, was not properly cleared in memory when saving the SVE state. The original fix used an unconditional 8-byte store to clear the FFR field, which either failed to clear the entire field or corrupted adjacent memory if the SME vector length was not 64 bytes. This could cause memory corruption and kernel faults. The vulnerability was fixed by replacing the 8-byte store with a store of a zero-initialized predicate register, ensuring the entire FFR field is properly cleared in memory.
How can this vulnerability impact me? :
This vulnerability can lead to memory corruption in the Linux kernel, which may cause intermittent kernel faults (kfence splats) and trigger memory corruption detection messages such as kmalloc Redzone overwrites. This can result in system instability, crashes, or unpredictable behavior when running workloads that use the affected SME streaming SVE mode, potentially impacting system reliability and security.
What immediate steps should I take to mitigate this vulnerability?
Apply the updated Linux kernel patch that replaces the unconditional 8-byte store with a store of a zero-initialised predicate register (PFALSE) to ensure the entire FFR field is cleared in memory, preventing memory corruption. Until the patch is applied, avoid running workloads or tests that trigger the vulnerability, such as the 'fp-stress' kselftest, to reduce the risk of kmalloc Redzone corruption.