{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90393 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90393 is an use after free vulnerability in Linux, published on 17 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-90393 and fix it if it is affected.\n\nWhat it is: CVE-2026-90393 is an use after free vulnerability in Linux, published on 17 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-90393 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-90393/ (Markdown: https://insights.sbomify.com/CVE-2026-90393/index.md)","id":"CVE-2026-90393","markdown":"https://insights.sbomify.com/CVE-2026-90393/index.md","name":"CVE-2026-90393","record":{"aliases":["AZL-101897","BELL-CVE-2026-90393","DEBIAN-CVE-2026-90393","GHSA-9prj-6xm5-hxjf","UBUNTU-CVE-2026-90393"],"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","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel's BPF netns link update allows local attackers to trigger a use-after-free, potentially leading to privilege escalation or code execution.","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\nbpf: Fix potential UAF in bpf_netns_link_update_prog\n\nIn bpf_netns_link_update_prog, the checks for old_prog and prog type\nare currently performed locklessly before acquiring netns_bpf_mutex.\nThis creates a race condition that can lead to a UAF issue.\n\nIf two threads concurrently execute BPF_LINK_UPDATE on the same netns\nlink, the following execution path can trigger a UAF:\n\nCPU0                                          CPU1\nbpf_netns_link_update_prog\n  if (old_prog \u0026\u0026 old_prog != link-\u003eprog)\n    return -EPERM;\n                                              bpf_netns_link_update_prog\n                                                if (old_prog \u0026\u0026 old_prog != link-\u003eprog)\n                                                ...\n                                                old_prog = xchg(\u0026link-\u003eprog, new_prog);\n                                                bpf_prog_put(old_prog);\n  if (new_prog-\u003etype != link-\u003eprog-\u003etype) \u003c-- trigger UAF\n\nFix this by moving the old_prog and prog-\u003etype checks inside the\nnetns_bpf_mutex critical section. Meanwhile, use guard() to simplify\nlock management and avoid all the goto jumping.","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":"bpf: Fix potential UAF in bpf_netns_link_update_prog","id":"CVE-2026-90393","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"power: supply: sc2731_charger: cancel work on remove","id":"CVE-2026-90394"},"packages":[],"prev":{"headline":"bpf: Fix potential UAF when reading bpf link info","id":"CVE-2026-90392"},"products":["Linux"],"published":"2026-09-17","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 the Linux kernel's BPF netns link update allows local attackers to trigger a use-after-free, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2026-90393/"}