{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54236 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54236 is a denial of service vulnerability in Linux, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-54236 and fix it if it is affected.\n\nWhat it is: CVE-2023-54236 is a denial of service vulnerability in Linux, published on 30 Dec 2025. 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-2023-54236 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-54236/ (Markdown: https://insights.sbomify.com/CVE-2023-54236/index.md)","id":"CVE-2023-54236","markdown":"https://insights.sbomify.com/CVE-2023-54236/index.md","name":"CVE-2023-54236","record":{"aliases":["BELL-CVE-2023-54236","DEBIAN-CVE-2023-54236","GHSA-9c88-mg4g-wxx2","UBUNTU-CVE-2023-54236"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A flaw in the Linux kernel net_failover module can cause a warning and potential instability when transmitting packets if the primary device has more than 16 TX queues.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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/net_failover: fix txq exceeding warning\n\nThe failover txq is inited as 16 queues.\nwhen a packet is transmitted from the failover device firstly,\nthe failover device will select the queue which is returned from\nthe primary device if the primary device is UP and running.\nIf the primary device txq is bigger than the default 16,\nit can lead to the following warning:\neth0 selects TX queue 18, but real number of TX queues is 16\n\nThe warning backtrace is:\n[   32.146376] CPU: 18 PID: 9134 Comm: chronyd Tainted: G            E      6.2.8-1.el7.centos.x86_64 #1\n[   32.147175] Hardware name: Red Hat KVM, BIOS 1.10.2-3.el7_4.1 04/01/2014\n[   32.147730] Call Trace:\n[   32.147971]  \u003cTASK\u003e\n[   32.148183]  dump_stack_lvl+0x48/0x70\n[   32.148514]  dump_stack+0x10/0x20\n[   32.148820]  netdev_core_pick_tx+0xb1/0xe0\n[   32.149180]  __dev_queue_xmit+0x529/0xcf0\n[   32.149533]  ? __check_object_size.part.0+0x21c/0x2c0\n[   32.149967]  ip_finish_output2+0x278/0x560\n[   32.150327]  __ip_finish_output+0x1fe/0x2f0\n[   32.150690]  ip_finish_output+0x2a/0xd0\n[   32.151032]  ip_output+0x7a/0x110\n[   32.151337]  ? __pfx_ip_finish_output+0x10/0x10\n[   32.151733]  ip_local_out+0x5e/0x70\n[   32.152054]  ip_send_skb+0x19/0x50\n[   32.152366]  udp_send_skb.isra.0+0x163/0x3a0\n[   32.152736]  udp_sendmsg+0xba8/0xec0\n[   32.153060]  ? __folio_memcg_unlock+0x25/0x60\n[   32.153445]  ? __pfx_ip_generic_getfrag+0x10/0x10\n[   32.153854]  ? sock_has_perm+0x85/0xa0\n[   32.154190]  inet_sendmsg+0x6d/0x80\n[   32.154508]  ? inet_sendmsg+0x6d/0x80\n[   32.154838]  sock_sendmsg+0x62/0x70\n[   32.155152]  ____sys_sendmsg+0x134/0x290\n[   32.155499]  ___sys_sendmsg+0x81/0xc0\n[   32.155828]  ? _get_random_bytes.part.0+0x79/0x1a0\n[   32.156240]  ? ip4_datagram_release_cb+0x5f/0x1e0\n[   32.156649]  ? get_random_u16+0x69/0xf0\n[   32.156989]  ? __fget_light+0xcf/0x110\n[   32.157326]  __sys_sendmmsg+0xc4/0x210\n[   32.157657]  ? __sys_connect+0xb7/0xe0\n[   32.157995]  ? __audit_syscall_entry+0xce/0x140\n[   32.158388]  ? syscall_trace_enter.isra.0+0x12c/0x1a0\n[   32.158820]  __x64_sys_sendmmsg+0x24/0x30\n[   32.159171]  do_syscall_64+0x38/0x90\n[   32.159493]  entry_SYSCALL_64_after_hwframe+0x72/0xdc\n\nFix that by reducing txq number as the non-existent primary-dev does.","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/net_failover: fix txq exceeding warning","id":"CVE-2023-54236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link()","id":"CVE-2023-54237"},"packages":[],"prev":{"headline":"PCI/DOE: Fix destroy_work_on_stack() race","id":"CVE-2023-54235"},"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 flaw in the Linux kernel net_failover module can cause a warning and potential instability when transmitting packets if the primary device has more than 16 TX queues.","url":"https://insights.sbomify.com/CVE-2023-54236/"}