{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-98775",
  "modified": "2026-10-19T04:30:01Z",
  "upstream": [
    "CVE-2026-98775"
  ],
  "published": "2026-10-18T15:54:51Z",
  "summary": "nitro_enclaves: fix use-after-free on SLOT_ALLOC failure",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnitro_enclaves: fix use-after-free on SLOT_ALLOC failure\n\nWhen ne_create_vm_ioctl() fails the SLOT_ALLOC request after\nanon_inode_getfile() has succeeded, the error path calls\nfput(enclave_file) and then frees ne_enclave.\n\nIn normal userspace context, fput() defers the final __fput() via\ntask_work. ne_enclave_release() therefore runs after ne_enclave has\nalready been freed and dereferences ne_enclave->slot_uid, causing a\nuse-after-free: KASAN: slab-use-after-free in ne_enclave_release.\n\nThe enclave has no slot allocated and is not yet linked into the\nenclaves list on this error path, so ne_enclave_release() is expected\nto return early when slot_uid is zero. However, reading slot_uid\nalready accesses the freed object.\n\nClear enclave_file->private_data before fput() on the error path.\nne_enclave_release() then returns immediately when private_data is\nNULL, leaving the ioctl error path as the sole owner of ne_enclave.\nThis is safe because the file has not been fd_install()'d yet.\n\nTested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the\npatch, the reproducer triggers a KASAN slab-use-after-free on every\nSLOT_ALLOC failure. With the patch, no KASAN report is produced and\nthe SLOT_ALLOC error is still returned. Normal enclave creation and\nteardown are unaffected.",
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-98775"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/466041d14f26dc2babd606a2e85dce08774112a6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f7fb6c2835ede1b8ad84cf7e78a528a9d0159b84"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/43f78b328f3907ca2f7424e15b7e45ffbf9fe21c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9bc184a2eda8b773c88ecbff934001ad649b9cc1"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-10-18T15:54:51Z"
  }
}