arm64/fpsimd: signal: Fix restoration of SVE context

{
  "id": "e2f0d0319b3837ab1ecbc6c54d7825cf78b7e13a05f86ad6086ed5930947e128",
  "url": "https://osv.dev/vulnerability/CVE-2026-23102",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "arm64/fpsimd: signal: Fix restoration of SVE context",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Fix restoration of SVE context When SME is supported, Restoring SVE signal context can go wrong in a few ways, including placing the task into an invalid state where the kernel may read from out-of-bounds memory (and may potentially take a fatal fault) and/or may kill the task with a SIGKILL. (1) Restoring a context with SVE_SIG_FLAG_SM set can place the task into an invalid state where SVCR.SM is set (and sve_state is non-NULL) but TIF_SME is clear, consequently resuting in out-of-bounds memory reads and/or killing the task with SIGKILL. This can only occur in unusual (but legitimate) cases where the SVE signal context has either been modified by userspace or was saved in the context of another task (e.g. as with CRIU), as otherwise the presence of an SVE signal context with SVE_SIG_FLAG_SM implies that TIF_SME is already set. While in this state, task_fpsimd_load() will NOT configure SMCR_ELx (leaving some arbitrary value configured in hardware) before restoring SVCR and attempting to restore the streaming mode SVE registers from memory via sve_load_state(). As the value of SMCR_ELx.LEN may be larger than the task's streaming SVE vector length, this may read memory outside of the task's allocated sve_state, reading unrelated data and/or triggering a fault. While this can result in secrets being loaded into streaming SVE registers, these values are never exposed. As TIF_SME is clear, fp",
    "evidence": "osv:CVE-2026-23102",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.1.162",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.123",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.8",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-23102",
      "aliases": [
        "CVE-2026-23102"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "85ed24dad2904f7c141911d91b7807ab02694b5e"
                },
                {
                  "fixed": "9bc3adba8c35119be80ab20217027720446742f2"
                },
                {
                  "fixed": "ce820dd4e6e2d711242dc4331713b9bb4fe06d09"
                },
                {
                  "fixed": "7b5a52cf252a0d2e89787b645290ad288878f332"
                },
                {
                  "fixed": "d2907cbe9ea0a54cbe078076f9d089240ee1e2d9"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23102.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.19.0"
                },
                {
                  "fixed": "6.1.162"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.123"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.18.8"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23102.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.414665811Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/7b5a52cf252a0d2e89787b645290ad288878f332",
        "https://git.kernel.org/stable/c/9bc3adba8c35119be80ab20217027720446742f2",
        "https://git.kernel.org/stable/c/ce820dd4e6e2d711242dc4331713b9bb4fe06d09",
        "https://git.kernel.org/stable/c/d2907cbe9ea0a54cbe078076f9d089240ee1e2d9",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23102.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-23102",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23102.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-23102",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 492780,
  "published_at": "2026-02-04T16:08:24.034+00:00"
}