{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92525 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92525 is a high-severity memory corruption 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-92525 and fix it if it is affected.\n\nWhat it is: CVE-2026-92525 is a high-severity memory corruption 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-92525 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-92525/ (Markdown: https://insights.sbomify.com/CVE-2026-92525/index.md)","id":"CVE-2026-92525","markdown":"https://insights.sbomify.com/CVE-2026-92525/index.md","name":"CVE-2026-92525","record":{"aliases":["AZL-102617","BELL-CVE-2026-92525","DEBIAN-CVE-2026-92525","GHSA-xqgc-mf52-qvg8","UBUNTU-CVE-2026-92525"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel RDMA","requires_auth":"low_privilege","summary":"A local unprivileged user can trigger an out-of-bounds read in the Linux kernel RDMA driver, causing a denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[]\n\nFor a user QP, qp-\u003esq.queue is a ring the application writes directly,\nso rxe_post_send() takes the is_user branch and only schedules send_task\nwithout validating the WQE. rxe_requester() consumes it in place via\nreq_next_wqe() and calls copy_data(), which indexes\n\u0026wqe-\u003edma.sge[cur_sge] with the attacker-controlled num_sge/cur_sge.\nOnly the kernel path bounds num_sge (validate_send_wr()); the user WQE\nis never checked, so a local unprivileged user can post a WQE with an\nout-of-range cur_sge or oversized num_sge and force an out-of-bounds\nread of the per-WQE sge array in copy_data() (vmalloc OOB read, local\nDoS).\n\nBound num_sge to qp-\u003esq.max_sge in rxe_requester() before use, the way\nget_srq_wqe() already guards SRQ entries, and bound cur_sge only when\nthe WQE carries payload (dma.resid): copy_data() returns early on a\nzero-length copy before touching dma-\u003esge[], so a zero-payload WQE --\nthe only kind a max_sge == 0 QP can post -- stays valid.\n\nReproduced under KASAN; the vmalloc-out-of-bounds in copy_data() is gone.","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/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[]","id":"CVE-2026-92525","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"itsourcecode Leave Management System index.php sql injection","id":"CVE-2026-92526"},"packages":[],"prev":{"headline":"irqchip/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc()","id":"CVE-2026-92524"},"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-19","vendors":["Linux"]},"summary":"A local unprivileged user can trigger an out-of-bounds read in the Linux kernel RDMA driver, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-92525/"}