{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93107 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93107 is a high-severity vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93107 and fix it if it is affected.\n\nWhat it is: CVE-2026-93107 is a high-severity vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93107 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-93107/ (Markdown: https://insights.sbomify.com/CVE-2026-93107/index.md)","id":"CVE-2026-93107","markdown":"https://insights.sbomify.com/CVE-2026-93107/index.md","name":"CVE-2026-93107","record":{"aliases":["AZL-101954","BELL-CVE-2026-93107","DEBIAN-CVE-2026-93107","GHSA-86fh-qj8h-2fhq","UBUNTU-CVE-2026-93107"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel RDMA","requires_auth":"none","summary":"A race condition in the Linux kernel RDMA driver causes duplicate packet processing and a null pointer dereference, leading to system crashes and data corruption.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state\n\nWhen do_complete() finds the QP in the error state it returns\nRESPST_CHK_RESOURCE.  Before commit 49dc9c1f0c7e (\"RDMA/rxe: Cleanup\nreset state handling in rxe_resp.c\") this was the flush loop:\ncheck_resource() had an error-state branch that fetched each remaining\nrecv WQE and completed it with IB_WC_WR_FLUSH_ERR, without touching\nthe current packet.  That commit removed the error-state branch from\ncheck_resource() (draining is now done at rxe_receiver() entry) but\nkept the do_complete() error-state return.\n\nAs a result, when a QP moves to the error state while a packet is\nbeing completed - e.g. an rdma_cm disconnect racing with receive\nprocessing - the responder state machine loops back into the request\nprocessing chain with the already-completed packet still in hand:\ncheck_resource() fetches a fresh recv WQE, execute()/send_data_in()\ncopies the same packet payload again, do_complete() posts another\nIB_WC_SUCCESS CQE (qp-\u003eresp.status is still 0), and control returns\nto the error-state check.  The loop re-executes the same packet once\nper posted recv WQE (observed: ~1000 duplicate IB_WC_SUCCESS\ncompletions of one SEND, one per ~8us, matching the RQ occupancy)\nuntil the RQ is exhausted, after which qp-\u003eresp.wqe is NULL and\nsend_data_in() dereferences it:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000014\n  Workqueue: rxe_wq do_work\n  RIP: copy_data+0x29/0x1f0\n  Call Trace:\n   send_data_in+0x25/0x50\n   rxe_receiver+0xf36/0x1dd0\n\nThe duplicate completions are indistinguishable from real receives to\nthe ULP.  During an rds stress test, the message was accepted as new and\ndelivered the same datagram to user space hundreds of times, corrupting\nthe stream; any ULP that relies on RC exactly-once delivery is affected.\n\nA live packet reaching the error-state check in do_complete() has\nbeen executed and completed exactly once and must be consumed, not\nre-processed.  Return RESPST_CLEANUP for it (dequeue and free); keep\nreturning RESPST_CHK_RESOURCE for the pkt == NULL case.","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: Avoid reprocessing the current packet after the QP enters the error state","id":"CVE-2026-93107","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":"RDMA/ipoib: Drain RCU callbacks during module teardown","id":"CVE-2026-93108"},"packages":[],"prev":{"headline":"crash_dump: release keyring reference at the correct time","id":"CVE-2026-93106"},"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 race condition in the Linux kernel RDMA driver causes duplicate packet processing and a null pointer dereference, leading to system crashes and data corruption.","url":"https://insights.sbomify.com/CVE-2026-93107/"}