{"id":"CVE-2026-98775","published":"2026-10-18T16:17:31.437","lastModified":"2026-10-19T10:19:41.597","description":"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.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/43f78b328f3907ca2f7424e15b7e45ffbf9fe21c","tags":[]},{"url":"https://git.kernel.org/stable/c/466041d14f26dc2babd606a2e85dce08774112a6","tags":[]},{"url":"https://git.kernel.org/stable/c/9bc184a2eda8b773c88ecbff934001ad649b9cc1","tags":[]},{"url":"https://git.kernel.org/stable/c/f7fb6c2835ede1b8ad84cf7e78a528a9d0159b84","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}