{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54004 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54004 is a high-severity vulnerability in Linux, published on 24 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-54004 and fix it if it is affected.\n\nWhat it is: CVE-2023-54004 is a high-severity vulnerability in Linux, published on 24 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-54004 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-54004/ (Markdown: https://insights.sbomify.com/CVE-2023-54004/index.md)","id":"CVE-2023-54004","markdown":"https://insights.sbomify.com/CVE-2023-54004/index.md","name":"CVE-2023-54004","record":{"aliases":["BELL-CVE-2023-54004","DEBIAN-CVE-2023-54004","GHSA-qcjw-844g-q2q4","UBUNTU-CVE-2023-54004"],"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 local attacker can cause a kernel crash via a NULL pointer dereference in the UDP-Lite protocol implementation.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nudplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().\n\nsyzbot reported [0] a null-ptr-deref in sk_get_rmem0() while using\nIPPROTO_UDPLITE (0x88):\n\n  14:25:52 executing program 1:\n  r0 = socket$inet6(0xa, 0x80002, 0x88)\n\nWe had a similar report [1] for probably sk_memory_allocated_add()\nin __sk_mem_raise_allocated(), and commit c915fe13cbaa (\"udplite: fix\nNULL pointer dereference\") fixed it by setting .memory_allocated for\nudplite_prot and udplitev6_prot.\n\nTo fix the variant, we need to set either .sysctl_wmem_offset or\n.sysctl_rmem.\n\nNow UDP and UDPLITE share the same value for .memory_allocated, so we\nuse the same .sysctl_wmem_offset for UDP and UDPLITE.\n\n[0]:\ngeneral protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN\nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\nCPU: 0 PID: 6829 Comm: syz-executor.1 Not tainted 6.4.0-rc2-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023\nRIP: 0010:sk_get_rmem0 include/net/sock.h:2907 [inline]\nRIP: 0010:__sk_mem_raise_allocated+0x806/0x17a0 net/core/sock.c:3006\nCode: c1 ea 03 80 3c 02 00 0f 85 23 0f 00 00 48 8b 44 24 08 48 8b 98 38 01 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 \u003c0f\u003e b6 14 02 48 89 d8 83 e0 07 83 c0 03 38 d0 0f 8d 6f 0a 00 00 8b\nRSP: 0018:ffffc90005d7f450 EFLAGS: 00010246\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffc90004d92000\nRDX: 0000000000000000 RSI: ffffffff88066482 RDI: ffffffff8e2ccbb8\nRBP: ffff8880173f7000 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: 0000000000030000\nR13: 0000000000000001 R14: 0000000000000340 R15: 0000000000000001\nFS:  0000000000000000(0000) GS:ffff8880b9800000(0063) knlGS:00000000f7f1cb40\nCS:  0010 DS: 002b ES: 002b CR0: 0000000080050033\nCR2: 000000002e82f000 CR3: 0000000034ff0000 CR4: 00000000003506f0\nCall Trace:\n \u003cTASK\u003e\n __sk_mem_schedule+0x6c/0xe0 net/core/sock.c:3077\n udp_rmem_schedule net/ipv4/udp.c:1539 [inline]\n __udp_enqueue_schedule_skb+0x776/0xb30 net/ipv4/udp.c:1581\n __udpv6_queue_rcv_skb net/ipv6/udp.c:666 [inline]\n udpv6_queue_rcv_one_skb+0xc39/0x16c0 net/ipv6/udp.c:775\n udpv6_queue_rcv_skb+0x194/0xa10 net/ipv6/udp.c:793\n __udp6_lib_mcast_deliver net/ipv6/udp.c:906 [inline]\n __udp6_lib_rcv+0x1bda/0x2bd0 net/ipv6/udp.c:1013\n ip6_protocol_deliver_rcu+0x2e7/0x1250 net/ipv6/ip6_input.c:437\n ip6_input_finish+0x150/0x2f0 net/ipv6/ip6_input.c:482\n NF_HOOK include/linux/netfilter.h:303 [inline]\n NF_HOOK include/linux/netfilter.h:297 [inline]\n ip6_input+0xa0/0xd0 net/ipv6/ip6_input.c:491\n ip6_mc_input+0x40b/0xf50 net/ipv6/ip6_input.c:585\n dst_input include/net/dst.h:468 [inline]\n ip6_rcv_finish net/ipv6/ip6_input.c:79 [inline]\n NF_HOOK include/linux/netfilter.h:303 [inline]\n NF_HOOK include/linux/netfilter.h:297 [inline]\n ipv6_rcv+0x250/0x380 net/ipv6/ip6_input.c:309\n __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5491\n __netif_receive_skb+0x1f/0x1c0 net/core/dev.c:5605\n netif_receive_skb_internal net/core/dev.c:5691 [inline]\n netif_receive_skb+0x133/0x7a0 net/core/dev.c:5750\n tun_rx_batched+0x4b3/0x7a0 drivers/net/tun.c:1553\n tun_get_user+0x2452/0x39c0 drivers/net/tun.c:1989\n tun_chr_write_iter+0xdf/0x200 drivers/net/tun.c:2035\n call_write_iter include/linux/fs.h:1868 [inline]\n new_sync_write fs/read_write.c:491 [inline]\n vfs_write+0x945/0xd50 fs/read_write.c:584\n ksys_write+0x12b/0x250 fs/read_write.c:637\n do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]\n __do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178\n do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203\n entry_SYSENTER_compat_after_hwframe+0x70/0x82\nRIP: 0023:0xf7f21579\nCode: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 \u003c5d\u003e 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00\n---truncated---","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":"udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().","id":"CVE-2023-54004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":7,"next":{"headline":"binder: fix memory leak in binder_init()","id":"CVE-2023-54005"},"packages":[],"prev":{"headline":"RDMA/core: Fix GID entry ref leak when create_ah fails","id":"CVE-2023-54003"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A local attacker can cause a kernel crash via a NULL pointer dereference in the UDP-Lite protocol implementation.","url":"https://insights.sbomify.com/CVE-2023-54004/"}