CVE-2023-53713 (GCVE-0-2023-53713)

Vulnerability from cvelistv5 – Published: 2025-10-22 13:23 – Updated: 2026-10-15 21:41
VLAI
Title
arm64: sme: Use STR P to clear FFR context field in streaming SVE mode
Summary
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
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SSVC
Exploitation: none Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-10-15 21:36 UTC
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6820 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 9f5848665788a0f07bc175cb2cdd06d367b7556e , < 97669214944e80d3756657c21c4f286f3da6a423 (git)
Affected: 9f5848665788a0f07bc175cb2cdd06d367b7556e , < 8769a62faacbbb6cac5e35d9047ce445183d4e9f (git)
Affected: 9f5848665788a0f07bc175cb2cdd06d367b7556e , < 1403a899153a12d93fd510e463fd6d0eafba4336 (git)
Affected: 9f5848665788a0f07bc175cb2cdd06d367b7556e , < 893b24181b4c4bf1fa2841b1ed192e5413a97cb1 (git)
guessed Create a notification for this product.
Linux Linux Affected: 5.16
Unaffected: 0 , < 5.16 (semver)
Unaffected: 6.1.39 , ≤ 6.1.* (semver)
Unaffected: 6.3.13 , ≤ 6.3.* (semver)
Unaffected: 6.4.4 , ≤ 6.4.* (semver)
Unaffected: 6.5 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2023-53713",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-15T21:36:42.451488Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-15T21:41:34.204Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/arm64/include/asm/fpsimdmacros.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "97669214944e80d3756657c21c4f286f3da6a423",
              "status": "affected",
              "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
              "versionType": "git"
            },
            {
              "lessThan": "8769a62faacbbb6cac5e35d9047ce445183d4e9f",
              "status": "affected",
              "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
              "versionType": "git"
            },
            {
              "lessThan": "1403a899153a12d93fd510e463fd6d0eafba4336",
              "status": "affected",
              "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
              "versionType": "git"
            },
            {
              "lessThan": "893b24181b4c4bf1fa2841b1ed192e5413a97cb1",
              "status": "affected",
              "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/arm64/include/asm/fpsimdmacros.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.16"
            },
            {
              "lessThan": "5.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.39",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.3.*",
              "status": "unaffected",
              "version": "6.3.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.4.*",
              "status": "unaffected",
              "version": "6.4.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.5",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.39",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.3.13",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.4.4",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.5",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: sme: Use STR P to clear FFR context field in streaming SVE mode\n\nThe FFR is a predicate register which can vary between 16 and 256 bits\nin size depending upon the configured vector length. When saving the\nSVE state in streaming SVE mode, the FFR register is inaccessible and\nso commit 9f5848665788 (\"arm64/sve: Make access to FFR optional\") simply\nclears the FFR field of the in-memory context structure. Unfortunately,\nit achieves this using an unconditional 8-byte store and so if the SME\nvector length is anything other than 64 bytes in size we will either\nfail to clear the entire field or, worse, we will corrupt memory\nimmediately following the structure. This has led to intermittent kfence\nsplats in CI [1] and can trigger kmalloc Redzone corruption messages\nwhen running the \u0027fp-stress\u0027 kselftest:\n\n | =============================================================================\n | BUG kmalloc-1k (Not tainted): kmalloc Redzone overwritten\n | -----------------------------------------------------------------------------\n |\n | 0xffff000809bf1e22-0xffff000809bf1e27 @offset=7714. First byte 0x0 instead of 0xcc\n | Allocated in do_sme_acc+0x9c/0x220 age=2613 cpu=1 pid=531\n |  __kmalloc+0x8c/0xcc\n |  do_sme_acc+0x9c/0x220\n |  ...\n\nReplace the 8-byte store with a store of a predicate register which has\nbeen zero-initialised with PFALSE, ensuring that the entire field is\ncleared in memory.\n\n[1] https://lore.kernel.org/r/CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Triggering requires executing code on the target: an unprivileged `prctl(PR_SME_SET_VL)` followed by an EL0 `SMSTART SM` instruction and a context switch. There is no remote or adjacent-network path to `fpsimd_save()`.\nAC:L - The attacker fully controls every triggering condition \u2014 the streaming vector length via prctl, entry into streaming SVE mode, and the context switch that invokes `sve_save_state()` \u2014 so the out-of-bounds store fires deterministically on every save, and the operation can be repeated in a tight loop to groom the slab.\nPR:L - `sme_set_current_vl()` and the SME access trap handler `do_sme_acc()` perform no capability or credential checks whatsoever; any ordinary unprivileged user process on an SME-capable system reaches the vulnerable store.\nUI:N - The attacking process triggers the save path entirely on its own via prctl plus an instruction; no victim action, file open, or mount is involved.\nS:U - The corruption occurs in the kernel\u0027s own slab allocation for the calling task\u0027s FP state, staying within the kernel\u0027s security authority \u2014 no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The out-of-bounds write past the end of a kmalloc\u0027d object is memory corruption of attacker-selectable allocation size, leverageable via heap grooming to zero length/pointer/refcount fields of a neighbouring object and thereby obtain kernel memory disclosure; additionally, for streaming vector lengths above 512 bits the FFR field is only partially cleared, and that stale in-kernel state is copied out to userspace through the SVE signal frame and the `NT_ARM_SSVE` ptrace regset.\nI:H - This is a heap out-of-bounds write \u2014 up to six zero bytes written beyond the end of a `kzalloc()`ed `task-\u003ethread.sve_state` buffer, confirmed in practice by kmalloc redzone-overwrite reports. Zeroing the leading bytes of an adjacent slab object (refcounts, pointers, flags) is a well-established primitive for corrupting kernel state and escalating privileges.\nA:H - The OOB store corrupts memory immediately following the slab object and produces kernel oopses in practice \u2014 the fix was prompted by intermittent KFENCE guard-page splats in CI, where the write lands on a guard page and faults at EL1, and SLUB redzone corruption detection can panic a hardened kernel."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T09:15:40.426Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/97669214944e80d3756657c21c4f286f3da6a423"
        },
        {
          "url": "https://git.kernel.org/stable/c/8769a62faacbbb6cac5e35d9047ce445183d4e9f"
        },
        {
          "url": "https://git.kernel.org/stable/c/1403a899153a12d93fd510e463fd6d0eafba4336"
        },
        {
          "url": "https://git.kernel.org/stable/c/893b24181b4c4bf1fa2841b1ed192e5413a97cb1"
        }
      ],
      "title": "arm64: sme: Use STR P to clear FFR context field in streaming SVE mode",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53713",
    "datePublished": "2025-10-22T13:23:47.720Z",
    "dateReserved": "2025-10-22T13:21:37.347Z",
    "dateUpdated": "2026-10-15T21:41:34.204Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2023-53713",
      "date": "2026-11-02",
      "epss": "0.00153",
      "percentile": "0.04382"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "arch/arm64/include/asm/fpsimdmacros.h"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "97669214944e80d3756657c21c4f286f3da6a423",
                    "status": "affected",
                    "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "8769a62faacbbb6cac5e35d9047ce445183d4e9f",
                    "status": "affected",
                    "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "1403a899153a12d93fd510e463fd6d0eafba4336",
                    "status": "affected",
                    "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "893b24181b4c4bf1fa2841b1ed192e5413a97cb1",
                    "status": "affected",
                    "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "arch/arm64/include/asm/fpsimdmacros.h"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "5.16"
                  },
                  {
                    "lessThan": "5.16",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.1.*",
                    "status": "unaffected",
                    "version": "6.1.39",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.3.*",
                    "status": "unaffected",
                    "version": "6.3.13",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.4.*",
                    "status": "unaffected",
                    "version": "6.4.4",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "6.5",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: sme: Use STR P to clear FFR context field in streaming SVE mode\n\nThe FFR is a predicate register which can vary between 16 and 256 bits\nin size depending upon the configured vector length. When saving the\nSVE state in streaming SVE mode, the FFR register is inaccessible and\nso commit 9f5848665788 (\"arm64/sve: Make access to FFR optional\") simply\nclears the FFR field of the in-memory context structure. Unfortunately,\nit achieves this using an unconditional 8-byte store and so if the SME\nvector length is anything other than 64 bytes in size we will either\nfail to clear the entire field or, worse, we will corrupt memory\nimmediately following the structure. This has led to intermittent kfence\nsplats in CI [1] and can trigger kmalloc Redzone corruption messages\nwhen running the \u0027fp-stress\u0027 kselftest:\n\n | =============================================================================\n | BUG kmalloc-1k (Not tainted): kmalloc Redzone overwritten\n | -----------------------------------------------------------------------------\n |\n | 0xffff000809bf1e22-0xffff000809bf1e27 @offset=7714. First byte 0x0 instead of 0xcc\n | Allocated in do_sme_acc+0x9c/0x220 age=2613 cpu=1 pid=531\n |  __kmalloc+0x8c/0xcc\n |  do_sme_acc+0x9c/0x220\n |  ...\n\nReplace the 8-byte store with a store of a predicate register which has\nbeen zero-initialised with PFALSE, ensuring that the entire field is\ncleared in memory.\n\n[1] https://lore.kernel.org/r/CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com"
          },
          {
            "lang": "es",
            "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\narm64: sme: Usar STR P para borrar el campo de contexto FFR en modo SVE de streaming\n\nEl FFR es un registro de predicado que puede variar entre 16 y 256 bits de tama\u00f1o dependiendo de la longitud de vector configurada. Al guardar el estado SVE en modo SVE de streaming, el registro FFR es inaccesible y por lo tanto el commit 9f5848665788 (\u2019arm64/sve: Hacer opcional el acceso a FFR\u2019) simplemente borra el campo FFR de la estructura de contexto en memoria. Desafortunadamente, lo logra usando un almacenamiento incondicional de 8 bytes y as\u00ed, si la longitud del vector SME es diferente de 64 bytes de tama\u00f1o, o no lograremos borrar el campo completo o, peor a\u00fan, corromperemos la memoria inmediatamente despu\u00e9s de la estructura. Esto ha provocado \u2019kfence splats\u2019 intermitentes en CI [1] y puede activar mensajes de corrupci\u00f3n de \u2019Redzone\u2019 de \u2019kmalloc\u2019 al ejecutar el \u2019kselftest\u2019 \u2019fp-stress\u2019:\n\n | =============================================================================\n | BUG kmalloc-1k (No contaminado): Redzone de kmalloc sobrescrita\n | -----------------------------------------------------------------------------\n |\n | 0xffff000809bf1e22-0xffff000809bf1e27 @offset=7714. Primer byte 0x0 en lugar de 0xcc\n | Asignado en do_sme_acc+0x9c/0x220 edad=2613 cpu=1 pid=531\n |  __kmalloc+0x8c/0xcc\n |  do_sme_acc+0x9c/0x220\n |  ...\n\nReemplazar el almacenamiento de 8 bytes con un almacenamiento de un registro de predicado que ha sido inicializado a cero con PFALSE, asegurando que todo el campo se borre en memoria.\n\n[1] https://lore.kernel.org/r/CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com"
          }
        ],
        "id": "CVE-2023-53713",
        "lastModified": "2026-10-28T19:10:00.193",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 7.8,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 5.9,
              "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2023-53713",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-15T21:36:42.451488Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2025-10-22T14:15:45.930",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/1403a899153a12d93fd510e463fd6d0eafba4336"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/8769a62faacbbb6cac5e35d9047ce445183d4e9f"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/893b24181b4c4bf1fa2841b1ed192e5413a97cb1"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/97669214944e80d3756657c21c4f286f3da6a423"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Deferred"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-10-30T02:51:16+00:00",
      "cve": "CVE-2023-53713",
      "id": "CVE-2023-53713",
      "initial_release_date": "2023-01-01T00:00:00+00:00",
      "product_status:fixed": "279",
      "product_status:known_affected": "70",
      "product_status:known_not_affected": "119",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: arm64: sme: Use STR P to clear FFR context field in streaming SVE mode",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2023/cve-2023-53713.json",
      "version": "3"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2023-53713",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "total"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-10-15T21:36:42.451488Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-10-15T21:36:42.955Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "unaffected",
              "product": "Linux",
              "programFiles": [
                "arch/arm64/include/asm/fpsimdmacros.h"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "lessThan": "97669214944e80d3756657c21c4f286f3da6a423",
                  "status": "affected",
                  "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                  "versionType": "git"
                },
                {
                  "lessThan": "8769a62faacbbb6cac5e35d9047ce445183d4e9f",
                  "status": "affected",
                  "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                  "versionType": "git"
                },
                {
                  "lessThan": "1403a899153a12d93fd510e463fd6d0eafba4336",
                  "status": "affected",
                  "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                  "versionType": "git"
                },
                {
                  "lessThan": "893b24181b4c4bf1fa2841b1ed192e5413a97cb1",
                  "status": "affected",
                  "version": "9f5848665788a0f07bc175cb2cdd06d367b7556e",
                  "versionType": "git"
                }
              ]
            },
            {
              "defaultStatus": "affected",
              "product": "Linux",
              "programFiles": [
                "arch/arm64/include/asm/fpsimdmacros.h"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "status": "affected",
                  "version": "5.16"
                },
                {
                  "lessThan": "5.16",
                  "status": "unaffected",
                  "version": "0",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "6.1.*",
                  "status": "unaffected",
                  "version": "6.1.39",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "6.3.*",
                  "status": "unaffected",
                  "version": "6.3.13",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "6.4.*",
                  "status": "unaffected",
                  "version": "6.4.4",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "*",
                  "status": "unaffected",
                  "version": "6.5",
                  "versionType": "original_commit_for_fix"
                }
              ]
            }
          ],
          "cpeApplicability": [
            {
              "nodes": [
                {
                  "cpeMatch": [
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.1.39",
                      "versionStartIncluding": "5.16",
                      "vulnerable": true
                    },
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.3.13",
                      "versionStartIncluding": "5.16",
                      "vulnerable": true
                    },
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.4.4",
                      "versionStartIncluding": "5.16",
                      "vulnerable": true
                    },
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.5",
                      "versionStartIncluding": "5.16",
                      "vulnerable": true
                    }
                  ],
                  "negate": false,
                  "operator": "OR"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: sme: Use STR P to clear FFR context field in streaming SVE mode\n\nThe FFR is a predicate register which can vary between 16 and 256 bits\nin size depending upon the configured vector length. When saving the\nSVE state in streaming SVE mode, the FFR register is inaccessible and\nso commit 9f5848665788 (\"arm64/sve: Make access to FFR optional\") simply\nclears the FFR field of the in-memory context structure. Unfortunately,\nit achieves this using an unconditional 8-byte store and so if the SME\nvector length is anything other than 64 bytes in size we will either\nfail to clear the entire field or, worse, we will corrupt memory\nimmediately following the structure. This has led to intermittent kfence\nsplats in CI [1] and can trigger kmalloc Redzone corruption messages\nwhen running the \u0027fp-stress\u0027 kselftest:\n\n | =============================================================================\n | BUG kmalloc-1k (Not tainted): kmalloc Redzone overwritten\n | -----------------------------------------------------------------------------\n |\n | 0xffff000809bf1e22-0xffff000809bf1e27 @offset=7714. First byte 0x0 instead of 0xcc\n | Allocated in do_sme_acc+0x9c/0x220 age=2613 cpu=1 pid=531\n |  __kmalloc+0x8c/0xcc\n |  do_sme_acc+0x9c/0x220\n |  ...\n\nReplace the 8-byte store with a store of a predicate register which has\nbeen zero-initialised with PFALSE, ensuring that the entire field is\ncleared in memory.\n\n[1] https://lore.kernel.org/r/CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com"
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 7.8,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "scenarios": [
                {
                  "lang": "en",
                  "value": "AV:L - Triggering requires executing code on the target: an unprivileged `prctl(PR_SME_SET_VL)` followed by an EL0 `SMSTART SM` instruction and a context switch. There is no remote or adjacent-network path to `fpsimd_save()`.\nAC:L - The attacker fully controls every triggering condition \u2014 the streaming vector length via prctl, entry into streaming SVE mode, and the context switch that invokes `sve_save_state()` \u2014 so the out-of-bounds store fires deterministically on every save, and the operation can be repeated in a tight loop to groom the slab.\nPR:L - `sme_set_current_vl()` and the SME access trap handler `do_sme_acc()` perform no capability or credential checks whatsoever; any ordinary unprivileged user process on an SME-capable system reaches the vulnerable store.\nUI:N - The attacking process triggers the save path entirely on its own via prctl plus an instruction; no victim action, file open, or mount is involved.\nS:U - The corruption occurs in the kernel\u0027s own slab allocation for the calling task\u0027s FP state, staying within the kernel\u0027s security authority \u2014 no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The out-of-bounds write past the end of a kmalloc\u0027d object is memory corruption of attacker-selectable allocation size, leverageable via heap grooming to zero length/pointer/refcount fields of a neighbouring object and thereby obtain kernel memory disclosure; additionally, for streaming vector lengths above 512 bits the FFR field is only partially cleared, and that stale in-kernel state is copied out to userspace through the SVE signal frame and the `NT_ARM_SSVE` ptrace regset.\nI:H - This is a heap out-of-bounds write \u2014 up to six zero bytes written beyond the end of a `kzalloc()`ed `task-\u003ethread.sve_state` buffer, confirmed in practice by kmalloc redzone-overwrite reports. Zeroing the leading bytes of an adjacent slab object (refcounts, pointers, flags) is a well-established primitive for corrupting kernel state and escalating privileges.\nA:H - The OOB store corrupts memory immediately following the slab object and produces kernel oopses in practice \u2014 the fix was prompted by intermittent KFENCE guard-page splats in CI, where the write lands on a guard page and faults at EL1, and SLUB redzone corruption detection can panic a hardened kernel."
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-05T09:15:40.426Z",
            "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "shortName": "Linux"
          },
          "references": [
            {
              "url": "https://git.kernel.org/stable/c/97669214944e80d3756657c21c4f286f3da6a423"
            },
            {
              "url": "https://git.kernel.org/stable/c/8769a62faacbbb6cac5e35d9047ce445183d4e9f"
            },
            {
              "url": "https://git.kernel.org/stable/c/1403a899153a12d93fd510e463fd6d0eafba4336"
            },
            {
              "url": "https://git.kernel.org/stable/c/893b24181b4c4bf1fa2841b1ed192e5413a97cb1"
            }
          ],
          "title": "arm64: sme: Use STR P to clear FFR context field in streaming SVE mode",
          "x_generator": {
            "engine": "bippy-1.2.0"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "assignerShortName": "Linux",
        "cveId": "CVE-2023-53713",
        "datePublished": "2025-10-22T13:23:47.720Z",
        "dateReserved": "2025-10-22T13:21:37.347Z",
        "dateUpdated": "2026-10-15T21:41:34.204Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.