{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89766 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89766 is a vulnerability in Linux, published on 11 Sep 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-89766 and fix it if it is affected.\n\nWhat it is: CVE-2026-89766 is a vulnerability in Linux, published on 11 Sep 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-89766 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-89766/ (Markdown: https://insights.sbomify.com/CVE-2026-89766/index.md)","id":"CVE-2026-89766","markdown":"https://insights.sbomify.com/CVE-2026-89766/index.md","name":"CVE-2026-89766","record":{"aliases":["BELL-CVE-2026-89766","DEBIAN-CVE-2026-89766","GHSA-7f3v-362v-5m4g","UBUNTU-CVE-2026-89766"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in Linux kernel pidfd namespace ioctls allows local attackers to bypass ptrace access checks and read restricted namespace information.","user_interaction":"not_required","vuln_class":"race_condition"},"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\npidfd: hold exec_update_lock around namespace ioctl\n\nThe PIDFD_GET_*_NAMESPACE ioctls in pidfd_ioctl() perform a filesystem\ncredentials ptrace access check before handing out a namespace file\ndescriptor.  The accompanying comment states that the code \"mirrors nsfs\nbehavior\", but, unlike the corresponding procfs paths, it does so without\nholding the target task's exec_update_lock.\n\nproc_ns_get_link() and proc_ns_readlink() both take exec_update_lock for\nreading around the ptrace check and the namespace lookup, so that the\ncredentials used for the access decision match those of the task when its\nnamespace is read.  Without it, a caller can pass the check against the\ntarget's old credentials and then read the namespace after the target has\nexecve()'d a setuid binary and committed new credentials -- accessing\nnamespace information it should have been denied.\n\nHold exec_update_lock for reading around the ptrace check and the\nnamespace lookup so that pidfd truly mirrors nsfs behavior, as the comment\nalready claims.  open_namespace() itself runs outside the lock: once a\nnamespace reference is obtained it carries its own refcount and is opened\nwith the caller's own credentials, so a concurrent execve() on the target\ncan no longer affect the outcome.","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":"pidfd: hold exec_update_lock around namespace ioctl","id":"CVE-2026-89766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ovl: fix double end_creating() on the casefold-mismatch path","id":"CVE-2026-89767"},"packages":[],"prev":{"headline":"timers/itimer: Zero-init old itimerval before copy to userspace","id":"CVE-2026-89765"},"products":["Linux"],"published":"2026-09-11","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-19","vendors":["Linux"]},"summary":"A race condition in Linux kernel pidfd namespace ioctls allows local attackers to bypass ptrace access checks and read restricted namespace information.","url":"https://insights.sbomify.com/CVE-2026-89766/"}