{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54094 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54094 is a critical 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-54094 and fix it if it is affected.\n\nWhat it is: CVE-2023-54094 is a critical 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-54094 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-54094/ (Markdown: https://insights.sbomify.com/CVE-2023-54094/index.md)","id":"CVE-2023-54094","markdown":"https://insights.sbomify.com/CVE-2023-54094/index.md","name":"CVE-2023-54094","record":{"aliases":["BELL-CVE-2023-54094","DEBIAN-CVE-2023-54094","GHSA-6wgm-8c2c-jvc6","UBUNTU-CVE-2023-54094"],"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 null pointer dereference in the Linux kernel network stack allows attackers to cause a system crash via crafted network packets.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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\nnet: prevent skb corruption on frag list segmentation\n\nIan reported several skb corruptions triggered by rx-gro-list,\ncollecting different oops alike:\n\n[   62.624003] BUG: kernel NULL pointer dereference, address: 00000000000000c0\n[   62.631083] #PF: supervisor read access in kernel mode\n[   62.636312] #PF: error_code(0x0000) - not-present page\n[   62.641541] PGD 0 P4D 0\n[   62.644174] Oops: 0000 [#1] PREEMPT SMP NOPTI\n[   62.648629] CPU: 1 PID: 913 Comm: napi/eno2-79 Not tainted 6.4.0 #364\n[   62.655162] Hardware name: Supermicro Super Server/A2SDi-12C-HLN4F, BIOS 1.7a 10/13/2022\n[   62.663344] RIP: 0010:__udp_gso_segment (./include/linux/skbuff.h:2858\n./include/linux/udp.h:23 net/ipv4/udp_offload.c:228 net/ipv4/udp_offload.c:261\nnet/ipv4/udp_offload.c:277)\n[   62.687193] RSP: 0018:ffffbd3a83b4f868 EFLAGS: 00010246\n[   62.692515] RAX: 00000000000000ce RBX: 0000000000000000 RCX: 0000000000000000\n[   62.699743] RDX: ffffa124def8a000 RSI: 0000000000000079 RDI: ffffa125952a14d4\n[   62.706970] RBP: ffffa124def8a000 R08: 0000000000000022 R09: 00002000001558c9\n[   62.714199] R10: 0000000000000000 R11: 00000000be554639 R12: 00000000000000e2\n[   62.721426] R13: ffffa125952a1400 R14: ffffa125952a1400 R15: 00002000001558c9\n[   62.728654] FS:  0000000000000000(0000) GS:ffffa127efa40000(0000)\nknlGS:0000000000000000\n[   62.736852] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   62.742702] CR2: 00000000000000c0 CR3: 00000001034b0000 CR4: 00000000003526e0\n[   62.749948] Call Trace:\n[   62.752498]  \u003cTASK\u003e\n[   62.779267] inet_gso_segment (net/ipv4/af_inet.c:1398)\n[   62.787605] skb_mac_gso_segment (net/core/gro.c:141)\n[   62.791906] __skb_gso_segment (net/core/dev.c:3403 (discriminator 2))\n[   62.800492] validate_xmit_skb (./include/linux/netdevice.h:4862\nnet/core/dev.c:3659)\n[   62.804695] validate_xmit_skb_list (net/core/dev.c:3710)\n[   62.809158] sch_direct_xmit (net/sched/sch_generic.c:330)\n[   62.813198] __dev_queue_xmit (net/core/dev.c:3805 net/core/dev.c:4210)\nnet/netfilter/core.c:626)\n[   62.821093] br_dev_queue_push_xmit (net/bridge/br_forward.c:55)\n[   62.825652] maybe_deliver (net/bridge/br_forward.c:193)\n[   62.829420] br_flood (net/bridge/br_forward.c:233)\n[   62.832758] br_handle_frame_finish (net/bridge/br_input.c:215)\n[   62.837403] br_handle_frame (net/bridge/br_input.c:298\nnet/bridge/br_input.c:416)\n[   62.851417] __netif_receive_skb_core.constprop.0 (net/core/dev.c:5387)\n[   62.866114] __netif_receive_skb_list_core (net/core/dev.c:5570)\n[   62.871367] netif_receive_skb_list_internal (net/core/dev.c:5638\nnet/core/dev.c:5727)\n[   62.876795] napi_complete_done (./include/linux/list.h:37\n./include/net/gro.h:434 ./include/net/gro.h:429 net/core/dev.c:6067)\n[   62.881004] ixgbe_poll (drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:3191)\n[   62.893534] __napi_poll (net/core/dev.c:6498)\n[   62.897133] napi_threaded_poll (./include/linux/netpoll.h:89\nnet/core/dev.c:6640)\n[   62.905276] kthread (kernel/kthread.c:379)\n[   62.913435] ret_from_fork (arch/x86/entry/entry_64.S:314)\n[   62.917119]  \u003c/TASK\u003e\n\nIn the critical scenario, rx-gro-list GRO-ed packets are fed, via a\nbridge, both to the local input path and to an egress device (tun).\n\nThe segmentation of such packets unsafely writes to the cloned skbs\nwith shared heads.\n\nThis change addresses the issue by uncloning as needed the\nto-be-segmented skbs.","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: prevent skb corruption on frag list segmentation","id":"CVE-2023-54094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"powerpc/iommu: Fix notifiers being shared by PCI and VIO buses","id":"CVE-2023-54095"},"packages":[],"prev":{"headline":"media: anysee: fix null-ptr-deref in anysee_master_xfer","id":"CVE-2023-54093"},"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":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel network stack allows attackers to cause a system crash via crafted network packets.","url":"https://insights.sbomify.com/CVE-2023-54094/"}