{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54302 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54302 is a vulnerability in Linux, published on 30 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-54302 and fix it if it is affected.\n\nWhat it is: CVE-2023-54302 is a vulnerability in Linux, published on 30 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-54302 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-54302/ (Markdown: https://insights.sbomify.com/CVE-2023-54302/index.md)","id":"CVE-2023-54302","markdown":"https://insights.sbomify.com/CVE-2023-54302/index.md","name":"CVE-2023-54302","record":{"aliases":["BELL-CVE-2023-54302","DEBIAN-CVE-2023-54302","GHSA-h862-m8hq-w46v","UBUNTU-CVE-2023-54302"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A data race in the Linux kernel's irdma driver can cause inconsistent statistics and potential logic bugs, requiring a kernel patch.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nRDMA/irdma: Fix data race on CQP completion stats\n\nCQP completion statistics is read lockesly in irdma_wait_event and\nirdma_check_cqp_progress while it can be updated in the completion\nthread irdma_sc_ccq_get_cqe_info on another CPU as KCSAN reports.\n\nMake completion statistics an atomic variable to reflect coherent updates\nto it. This will also avoid load/store tearing logic bug potentially\npossible by compiler optimizations.\n\n[77346.170861] BUG: KCSAN: data-race in irdma_handle_cqp_op [irdma] / irdma_sc_ccq_get_cqe_info [irdma]\n\n[77346.171383] write to 0xffff8a3250b108e0 of 8 bytes by task 9544 on cpu 4:\n[77346.171483]  irdma_sc_ccq_get_cqe_info+0x27a/0x370 [irdma]\n[77346.171658]  irdma_cqp_ce_handler+0x164/0x270 [irdma]\n[77346.171835]  cqp_compl_worker+0x1b/0x20 [irdma]\n[77346.172009]  process_one_work+0x4d1/0xa40\n[77346.172024]  worker_thread+0x319/0x700\n[77346.172037]  kthread+0x180/0x1b0\n[77346.172054]  ret_from_fork+0x22/0x30\n\n[77346.172136] read to 0xffff8a3250b108e0 of 8 bytes by task 9838 on cpu 2:\n[77346.172234]  irdma_handle_cqp_op+0xf4/0x4b0 [irdma]\n[77346.172413]  irdma_cqp_aeq_cmd+0x75/0xa0 [irdma]\n[77346.172592]  irdma_create_aeq+0x390/0x45a [irdma]\n[77346.172769]  irdma_rt_init_hw.cold+0x212/0x85d [irdma]\n[77346.172944]  irdma_probe+0x54f/0x620 [irdma]\n[77346.173122]  auxiliary_bus_probe+0x66/0xa0\n[77346.173137]  really_probe+0x140/0x540\n[77346.173154]  __driver_probe_device+0xc7/0x220\n[77346.173173]  driver_probe_device+0x5f/0x140\n[77346.173190]  __driver_attach+0xf0/0x2c0\n[77346.173208]  bus_for_each_dev+0xa8/0xf0\n[77346.173225]  driver_attach+0x29/0x30\n[77346.173240]  bus_add_driver+0x29c/0x2f0\n[77346.173255]  driver_register+0x10f/0x1a0\n[77346.173272]  __auxiliary_driver_register+0xbc/0x140\n[77346.173287]  irdma_init_module+0x55/0x1000 [irdma]\n[77346.173460]  do_one_initcall+0x7d/0x410\n[77346.173475]  do_init_module+0x81/0x2c0\n[77346.173491]  load_module+0x1232/0x12c0\n[77346.173506]  __do_sys_finit_module+0x101/0x180\n[77346.173522]  __x64_sys_finit_module+0x3c/0x50\n[77346.173538]  do_syscall_64+0x39/0x90\n[77346.173553]  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\n[77346.173634] value changed: 0x0000000000000094 -\u003e 0x0000000000000095","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/irdma: Fix data race on CQP completion stats","id":"CVE-2023-54302","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":"bpf: Disable preemption in bpf_perf_event_output","id":"CVE-2023-54303"},"packages":[],"prev":{"headline":"serial: 8250_bcm7271: fix leak in `brcmuart_probe`","id":"CVE-2023-54301"},"products":["Linux"],"published":"2025-12-30","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-05-11","vendors":["Linux"]},"summary":"A data race in the Linux kernel's irdma driver can cause inconsistent statistics and potential logic bugs, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2023-54302/"}