{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92517 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92517 is a 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-92517 and fix it if it is affected.\n\nWhat it is: CVE-2026-92517 is a 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-92517 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-92517/ (Markdown: https://insights.sbomify.com/CVE-2026-92517/index.md)","id":"CVE-2026-92517","markdown":"https://insights.sbomify.com/CVE-2026-92517/index.md","name":"CVE-2026-92517","record":{"aliases":["BELL-CVE-2026-92517","DEBIAN-CVE-2026-92517","GHSA-92r6-5jjc-jv43","UBUNTU-CVE-2026-92517"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can leak stale register data via BPF arena load_acquire faults or cause a kernel oops due to missing exception handling in the RISC-V Linux kernel.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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, riscv: Fix extable handling for arena load_acquire\n\nemit_atomic_ld_st() returns 1 to have build_body() skip the zext after\na sub-word load_acquire. The caller does \"ret = ret ?:\nadd_exception_handler(...)\", which skips add_exception_handler() on any\nnon-zero ret, so the extable entry is missing and a faulting\nPROBE_ATOMIC load_acquire oopses.\n\nREG_DONT_CLEAR_MARKER leaves rd stale on fault, and the verifier still\nthinks the load overwrote it, so a program can leak it through a map.\n\nCheck ret \u003e= 0 before calling add_exception_handler(), and pass rd for\nLOAD_ACQ so the fault zeroes rd like a PROBE_MEM load. Return ret\nunchanged for the zext skip.","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, riscv: Fix extable handling for arena load_acquire","id":"CVE-2026-92517","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"riscv, bpf: Fix kernel stack corruption in tailcall with CFI","id":"CVE-2026-92518"},"packages":[],"prev":{"headline":"bpf: Fix offset warn check for bpf_res_spin_lock","id":"CVE-2026-92516"},"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 local attacker can leak stale register data via BPF arena load_acquire faults or cause a kernel oops due to missing exception handling in the RISC-V Linux kernel.","url":"https://insights.sbomify.com/CVE-2026-92517/"}