{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54048 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54048 is a high-severity vulnerability in Linux, published on 24 Dec 2025. 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-2023-54048 and fix it if it is affected.\n\nWhat it is: CVE-2023-54048 is a high-severity vulnerability in Linux, published on 24 Dec 2025. 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-2023-54048 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-2023-54048/ (Markdown: https://insights.sbomify.com/CVE-2023-54048/index.md)","id":"CVE-2023-54048","markdown":"https://insights.sbomify.com/CVE-2023-54048/index.md","name":"CVE-2023-54048","record":{"aliases":["BELL-CVE-2023-54048","DEBIAN-CVE-2023-54048","GHSA-4gfv-wqf7-r3g7","ROOT-OS-DEBIAN-11-CVE-2023-54048","UBUNTU-CVE-2023-54048"],"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 driver","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel RDMA driver allows a kernel panic when completion handlers run after queue pair destruction.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nRDMA/bnxt_re: Prevent handling any completions after qp destroy\n\nHW may generate completions that indicates QP is destroyed.\nDriver should not be scheduling any more completion handlers\nfor this QP, after the QP is destroyed. Since CQs are active\nduring the QP destroy, driver may still schedule completion\nhandlers. This can cause a race where the destroy_cq and poll_cq\nrunning simultaneously.\n\nSnippet of kernel panic while doing bnxt_re driver load unload in loop.\nThis indicates a poll after the CQ is freed. \n\n[77786.481636] Call Trace:\n[77786.481640]  \u003cTASK\u003e\n[77786.481644]  bnxt_re_poll_cq+0x14a/0x620 [bnxt_re]\n[77786.481658]  ? kvm_clock_read+0x14/0x30\n[77786.481693]  __ib_process_cq+0x57/0x190 [ib_core]\n[77786.481728]  ib_cq_poll_work+0x26/0x80 [ib_core]\n[77786.481761]  process_one_work+0x1e5/0x3f0\n[77786.481768]  worker_thread+0x50/0x3a0\n[77786.481785]  ? __pfx_worker_thread+0x10/0x10\n[77786.481790]  kthread+0xe2/0x110\n[77786.481794]  ? __pfx_kthread+0x10/0x10\n[77786.481797]  ret_from_fork+0x2c/0x50\n\nTo avoid this, complete all completion handlers before returning the\ndestroy QP. If free_cq is called soon after destroy_qp,  IB stack\nwill cancel the CQ work before invoking the destroy_cq verb and\nthis will prevent any race mentioned.","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/bnxt_re: Prevent handling any completions after qp destroy","id":"CVE-2023-54048","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"rpmsg: glink: Add check for kstrdup","id":"CVE-2023-54049"},"packages":[],"prev":{"headline":"drm/rockchip: dw_hdmi: cleanup drm encoder during unbind","id":"CVE-2023-54047"},"products":["Linux"],"published":"2025-12-24","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A race condition in the Linux kernel RDMA driver allows a kernel panic when completion handlers run after queue pair destruction.","url":"https://insights.sbomify.com/CVE-2023-54048/"}