{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92485 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92485 is a high-severity 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-92485 and fix it if it is affected.\n\nWhat it is: CVE-2026-92485 is a high-severity 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-92485 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-92485/ (Markdown: https://insights.sbomify.com/CVE-2026-92485/index.md)","id":"CVE-2026-92485","markdown":"https://insights.sbomify.com/CVE-2026-92485/index.md","name":"CVE-2026-92485","record":{"aliases":["AZL-102357","BELL-CVE-2026-92485","DEBIAN-CVE-2026-92485","GHSA-hhjv-qj57-f47f","UBUNTU-CVE-2026-92485"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel BPF","requires_auth":"low_privilege","summary":"A logic error in the Linux kernel BPF subsystem causes a kernel warning and potential crash when releasing tracing links, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix WARNING in bpf_tracing_link_release\n\nThe trampoline could be corrupted by the blindly\n'tr-\u003eflags = BPF_TRAMP_F_TAIL_CALL_CTX' in verifier.\n\n1. A fexit attached to a tail_call_reachable prog. 'tr-\u003eflags' became\n   'BPF_TRAMP_F_CALL_ORIG | BPF_TRAMP_F_TAIL_CALL_CTX'. And, the\n   trampoline would poke the target prog's nop insn using jmp insn instead\n   of call insn.\n2. Another fexit loaded with the same tail_call_reachable prog target.\n   'tr-\u003eflags' became 'BPF_TRAMP_F_TAIL_CALL_CTX'.\n3. Close the first fexit link. Due to no BPF_TRAMP_F_CALL_ORIG in\n   'tr-\u003eflags', the trampoline will fail to restore the prog's nop insn\n   using call insn.\n\n[    3.410719] WARNING: kernel/bpf/syscall.c:3551 at bpf_tracing_link_release+0x53/0x60, CPU#1: test_progs/98\n...\n[    3.428793]  bpf_link_free+0x58/0x130\n[    3.429293]  bpf_link_release+0x23/0x30\n\nFix the warning by updating 'tr-\u003eflags' with '|=' and lock.","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 WARNING in bpf_tracing_link_release","id":"CVE-2026-92485","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"bpf: Fix CFI mismatch in task work callback","id":"CVE-2026-92486"},"packages":[],"prev":{"headline":"cxl/region: Fix use-after-free in find_pos_and_ways() error path","id":"CVE-2026-92484"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A logic error in the Linux kernel BPF subsystem causes a kernel warning and potential crash when releasing tracing links, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-92485/"}