Live › vulnerability › CVE-2026-98775
Go to dashboardA flaw in the Linux kernel's nitro_enclaves driver frees an enclave object and then reads it again when slot allocation fails during VM creation. The sources do not say what an attacker can gain beyond a memory-safety crash and use-after-free.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only systems running the Linux kernel nitro_enclaves driver, which is used on AWS EC2 Nitro Enclaves hosts, are in scope. Hosts without this driver loaded can likely skip it, but the sources do not confirm that.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel releases in the upstream commit.lsmod | grep nitro_enclaves.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
nitro_enclaves: fix use-after-free on SLOT_ALLOC failure
When ne_create_vm_ioctl() fails the SLOT_ALLOC request after anon_inode_getfile() has succeeded, the error path calls fput(enclave_file) and then frees ne_enclave.
In normal userspace context, fput() defers the final __fput() via task_work. ne_enclave_release() therefore runs after ne_enclave has already been freed and dereferences ne_enclave->slot_uid, causing a use-after-free: KASAN: slab-use-after-free in ne_enclave_release.
The enclave has no slot allocated and is not yet linked into the enclaves list on this error path, so ne_enclave_release() is expected to return early when slot_uid is zero. However, reading slot_uid already accesses the freed object.
Clear enclave_file->private_data before fput() on the error path. ne_enclave_release() then returns immediately when private_data is NULL, leaving the ioctl error path as the sole owner of ne_enclave. This is safe because the file has not been fd_install()'d yet.
Tested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the patch, the reproducer triggers a KASAN slab-use-after-free on every SLOT_ALLOC failure. With the patch, no KASAN report is produced and the SLOT_ALLOC error is still returned. Normal enclave creation and teardown are unaffected.
This page as .md · .json · in your agent: get_signal("CVE-2026-98775")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.