{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92509 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92509 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-92509 and fix it if it is affected.\n\nWhat it is: CVE-2026-92509 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-92509 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-92509/ (Markdown: https://insights.sbomify.com/CVE-2026-92509/index.md)","id":"CVE-2026-92509","markdown":"https://insights.sbomify.com/CVE-2026-92509/index.md","name":"CVE-2026-92509","record":{"aliases":["AZL-102183","BELL-CVE-2026-92509","DEBIAN-CVE-2026-92509","GHSA-w9c6-3cwc-m3q4","UBUNTU-CVE-2026-92509"],"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 RDMA","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel RDMA core allows local attackers to potentially execute code or escalate privileges via netlink counter access.","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\nRDMA/core: Fix potential use after free in counter_release()\n\nWhen accessing a counter via the netlink path the only synchronization\nmechanism for the said counter is rdma_restrack_get().\nCurrently, rdma_restrack_del() is invoked at the end of\ncounter_release(), which is too late, since by that point\nvendor-specific resources associated with the counter might already be\nfreed. This can leave a short window where the counter remains\naccessible through restrack, leading to a potential use-after-free.\n\nFix this by moving the rdma_restrack_del() call to be before the\nfreeing of the vendor-specific resources, ensuring that the counter is\nremoved from restrack before its internal resources are released.\nThis guarantees that no new users hold references to a counter that is\nin the process of destruction.","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":"RDMA/core: Fix potential use after free in counter_release()","id":"CVE-2026-92509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"RDMA/core: Fix potential use after free in ib_destroy_srq_user()","id":"CVE-2026-92510"},"packages":[],"prev":{"headline":"RDMA/core: Fix potential use after free in ib_free_cq()","id":"CVE-2026-92508"},"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 use-after-free in the Linux kernel RDMA core allows local attackers to potentially execute code or escalate privileges via netlink counter access.","url":"https://insights.sbomify.com/CVE-2026-92509/"}