{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54000 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54000 is a 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-54000 and fix it if it is affected.\n\nWhat it is: CVE-2023-54000 is a 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-54000 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-54000/ (Markdown: https://insights.sbomify.com/CVE-2023-54000/index.md)","id":"CVE-2023-54000","markdown":"https://insights.sbomify.com/CVE-2023-54000/index.md","name":"CVE-2023-54000","record":{"aliases":["BELL-CVE-2023-54000","DEBIAN-CVE-2023-54000","GHSA-vv3g-hqvr-cpcf","UBUNTU-CVE-2023-54000"],"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":"low_privilege","summary":"A race condition in the hns3 network driver causes a deadlock when external loopback and reset operations occur simultaneously, leading to system hang.","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\nnet: hns3: fix deadlock issue when externel_lb and reset are executed together\n\nWhen externel_lb and reset are executed together, a deadlock may\noccur:\n[ 3147.217009] INFO: task kworker/u321:0:7 blocked for more than 120 seconds.\n[ 3147.230483] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 3147.238999] task:kworker/u321:0  state:D stack:    0 pid:    7 ppid:     2 flags:0x00000008\n[ 3147.248045] Workqueue: hclge hclge_service_task [hclge]\n[ 3147.253957] Call trace:\n[ 3147.257093]  __switch_to+0x7c/0xbc\n[ 3147.261183]  __schedule+0x338/0x6f0\n[ 3147.265357]  schedule+0x50/0xe0\n[ 3147.269185]  schedule_preempt_disabled+0x18/0x24\n[ 3147.274488]  __mutex_lock.constprop.0+0x1d4/0x5dc\n[ 3147.279880]  __mutex_lock_slowpath+0x1c/0x30\n[ 3147.284839]  mutex_lock+0x50/0x60\n[ 3147.288841]  rtnl_lock+0x20/0x2c\n[ 3147.292759]  hclge_reset_prepare+0x68/0x90 [hclge]\n[ 3147.298239]  hclge_reset_subtask+0x88/0xe0 [hclge]\n[ 3147.303718]  hclge_reset_service_task+0x84/0x120 [hclge]\n[ 3147.309718]  hclge_service_task+0x2c/0x70 [hclge]\n[ 3147.315109]  process_one_work+0x1d0/0x490\n[ 3147.319805]  worker_thread+0x158/0x3d0\n[ 3147.324240]  kthread+0x108/0x13c\n[ 3147.328154]  ret_from_fork+0x10/0x18\n\nIn externel_lb process, the hns3 driver call napi_disable()\nfirst, then the reset happen, then the restore process of the\nexternel_lb will fail, and will not call napi_enable(). When\ndoing externel_lb again, napi_disable() will be double call,\ncause a deadlock of rtnl_lock().\n\nThis patch use the HNS3_NIC_STATE_DOWN state to protect the\ncalling of napi_disable() and napi_enable() in externel_lb\nprocess, just as the usage in ndo_stop() and ndo_start().","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":"net: hns3: fix deadlock issue when externel_lb and reset are executed together","id":"CVE-2023-54000","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":"staging: r8712: Fix memory leak in _r8712_init_xmit_priv()","id":"CVE-2023-54001"},"packages":[],"prev":{"headline":"net/mlx5e: TC, Fix internal port memory leak","id":"CVE-2023-53999"},"products":["Linux"],"published":"2025-12-24","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 race condition in the hns3 network driver causes a deadlock when external loopback and reset operations occur simultaneously, leading to system hang.","url":"https://insights.sbomify.com/CVE-2023-54000/"}