{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98775 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98775 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98775 and fix it if it is affected.\n\nWhat it is: CVE-2026-98775 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98775 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98775/ (Markdown: https://insights.sbomify.com/CVE-2026-98775/index.md)","id":"CVE-2026-98775","markdown":"https://insights.sbomify.com/CVE-2026-98775/index.md","name":"CVE-2026-98775","record":{"aliases":["AZL-109094","BELL-CVE-2026-98775","DEBIAN-CVE-2026-98775","GHSA-8pj3-87fr-9h94","UBUNTU-CVE-2026-98775"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel nitro_enclaves driver allows local attackers to potentially execute code or escalate privileges via a specific ioctl failure path.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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-\u003eslot_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-\u003eprivate_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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nitro_enclaves: fix use-after-free on SLOT_ALLOC failure","id":"CVE-2026-98775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"binderfs: fix UAF write in binder_add_device","id":"CVE-2026-98776"},"packages":[],"prev":{"headline":"rust_binder: cancel deferred work items in thread exit","id":"CVE-2026-98774"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel nitro_enclaves driver allows local attackers to potentially execute code or escalate privileges via a specific ioctl failure path.","url":"https://insights.sbomify.com/CVE-2026-98775/"}