CVE-2023-54094

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-24. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net: prevent skb corruption on frag list segmentation

Ian reported several skb corruptions triggered by rx-gro-list, collecting different oops alike:

[ 62.624003] BUG: kernel NULL pointer dereference, address: 00000000000000c0 [ 62.631083] #PF: supervisor read access in kernel mode [ 62.636312] #PF: error_code(0x0000) - not-present page [ 62.641541] PGD 0 P4D 0 [ 62.644174] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 62.648629] CPU: 1 PID: 913 Comm: napi/eno2-79 Not tainted 6.4.0 #364 [ 62.655162] Hardware name: Supermicro Super Server/A2SDi-12C-HLN4F, BIOS 1.7a 10/13/2022 [ 62.663344] RIP: 0010:__udp_gso_segment (./include/linux/skbuff.h:2858 ./include/linux/udp.h:23 net/ipv4/udp_offload.c:228 net/ipv4/udp_offload.c:261 net/ipv4/udp_offload.c:277) [ 62.687193] RSP: 0018:ffffbd3a83b4f868 EFLAGS: 00010246 [ 62.692515] RAX: 00000000000000ce RBX: 0000000000000000 RCX: 0000000000000000 [ 62.699743] RDX: ffffa124def8a000 RSI: 0000000000000079 RDI: ffffa125952a14d4 [ 62.706970] RBP: ffffa124def8a000 R08: 0000000000000022 R09: 00002000001558c9 [ 62.714199] R10: 0000000000000000 R11: 00000000be554639 R12: 00000000000000e2 [ 62.721426] R13: ffffa125952a1400 R14: ffffa125952a1400 R15: 00002000001558c9 [ 62.728654] FS: 0000000000000000(0000) GS:ffffa127efa40000(0000) knlGS:0000000000000000 [ 62.736852] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 62.742702] CR2: 00000000000000c0 CR3: 00000001034b0000 CR4: 00000000003526e0 [ 62.749948] Call Trace: [ 62.752498] [ 62.779267] inet_gso_segment (net/ipv4/af_inet.c:1398) [ 62.787605] skb_mac_gso_segment (net/core/gro.c:141) [ 62.791906] __skb_gso_segment (net/core/dev.c:3403 (discriminator 2)) [ 62.800492] validate_xmit_skb (./include/linux/netdevice.h:4862 net/core/dev.c:3659) [ 62.804695] validate_xmit_skb_list (net/core/dev.c:3710) [ 62.809158] sch_direct_xmit (net/sched/sch_generic.c:330) [ 62.813198] __dev_queue_xmit (net/core/dev.c:3805 net/core/dev.c:4210) net/netfilter/core.c:626) [ 62.821093] br_dev_queue_push_xmit (net/bridge/br_forward.c:55) [ 62.825652] maybe_deliver (net/bridge/br_forward.c:193) [ 62.829420] br_flood (net/bridge/br_forward.c:233) [ 62.832758] br_handle_frame_finish (net/bridge/br_input.c:215) [ 62.837403] br_handle_frame (net/bridge/br_input.c:298 net/bridge/br_input.c:416) [ 62.851417] __netif_receive_skb_core.constprop.0 (net/core/dev.c:5387) [ 62.866114] __netif_receive_skb_list_core (net/core/dev.c:5570) [ 62.871367] netif_receive_skb_list_internal (net/core/dev.c:5638 net/core/dev.c:5727) [ 62.876795] napi_complete_done (./include/linux/list.h:37 ./include/net/gro.h:434 ./include/net/gro.h:429 net/core/dev.c:6067) [ 62.881004] ixgbe_poll (drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:3191) [ 62.893534] __napi_poll (net/core/dev.c:6498) [ 62.897133] napi_threaded_poll (./include/linux/netpoll.h:89 net/core/dev.c:6640) [ 62.905276] kthread (kernel/kthread.c:379) [ 62.913435] ret_from_fork (arch/x86/entry/entry_64.S:314) [ 62.917119]

In the critical scenario, rx-gro-list GRO-ed packets are fed, via a bridge, both to the local input path and to an egress device (tun).

The segmentation of such packets unsafely writes to the cloned skbs with shared heads.

This change addresses the issue by uncloning as needed the to-be-segmented skbs.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

net: prevent skb corruption on frag list segmentation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c329b261afe71197d9da83c1f18eb45a7e97e089
generic

net: prevent skb corruption on frag list segmentation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a59f29961cf97b98b02acaadf5a0b1f8dde938c
generic

net: prevent skb corruption on frag list segmentation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1731234e8b60063eae858c77b55c7a88f5084353
generic

net: prevent skb corruption on frag list segmentation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea438eed94ac0fe69b93ac034738823c0e989a12
generic

net: prevent skb corruption on frag list segmentation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bc3ab5d2ab69823f5cff89cf74ef78ffa0386c9a

Vendor Advisories for CVE-2023-54094(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.188—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (33 versions)5.10.191-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)6.1.52-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-20 20:14 UTCEPSS rescore
  2. 2026-09-20 20:14 UTCEPSS rescore
  3. 2026-09-18 19:26 UTCEPSS rescore
  4. 2026-09-16 14:06 UTCEPSS rescore
  5. 2026-09-16 05:11 UTCEPSS rescore
  6. 2026-09-16 05:11 UTCEPSS rescore
  7. 2026-09-15 03:08 UTCEPSS rescore
  8. 2026-09-14 05:49 UTCOSV refresh
  9. 2026-09-13 16:45 UTCEPSS rescore
  10. 2026-09-12 14:58 UTCEPSS rescore
  11. 2026-09-11 14:51 UTCEPSS rescore
  12. 2026-09-11 09:34 UTCEPSS rescore
  13. 2026-09-08 21:58 UTCEPSS rescore
  14. 2026-09-07 15:59 UTCEPSS rescore
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-05 15:26 UTCEPSS rescore
  17. 2026-09-04 13:58 UTCEPSS rescore
  18. 2026-09-04 05:04 UTCEPSS rescore
  19. 2026-09-02 14:10 UTCEPSS rescore
  20. 2026-09-01 13:52 UTCEPSS rescore
  21. 2026-09-01 04:36 UTCEPSS rescore
  22. 2026-08-30 19:15 UTCEPSS rescore
  23. 2026-08-30 01:20 UTCEPSS rescore
  24. 2026-08-28 21:39 UTCEPSS rescore
  25. 2026-08-27 14:23 UTCEPSS rescore
Show 75 more
  1. 2026-08-26 14:44 UTCEPSS rescore
  2. 2026-08-26 06:43 UTCOSV refresh
  3. 2026-08-25 13:47 UTCEPSS rescore
  4. 2026-08-23 00:17 UTCEPSS rescore
  5. 2026-08-23 00:17 UTCEPSS rescore
  6. 2026-08-21 23:47 UTCEPSS rescore
  7. 2026-08-20 22:53 UTCEPSS rescore
  8. 2026-08-19 17:02 UTCEPSS rescore
  9. 2026-08-18 13:46 UTCEPSS rescore
  10. 2026-08-16 14:54 UTCEPSS rescore
  11. 2026-08-16 02:12 UTCEPSS rescore
  12. 2026-08-15 01:28 UTCEPSS rescore
  13. 2026-08-13 21:58 UTCEPSS rescore
  14. 2026-08-12 13:49 UTCEPSS rescore
  15. 2026-08-11 13:40 UTCEPSS rescore
  16. 2026-08-10 23:58 UTCEPSS rescore
  17. 2026-08-09 22:47 UTCEG score recompute
  18. 2026-08-09 22:47 UTCGHSA enrichment
  19. 2026-08-09 13:44 UTCEPSS rescore
  20. 2026-08-08 09:17 UTCGHSA enrichment
  21. 2026-08-08 05:27 UTCEG score recompute
  22. 2026-08-08 05:27 UTCGHSA enrichment
  23. 2026-08-07 16:25 UTCEPSS rescore
  24. 2026-08-06 13:45 UTCEPSS rescore
  25. 2026-08-06 07:10 UTCEG score recompute
  26. 2026-08-06 07:10 UTCGHSA enrichment
  27. 2026-08-05 19:15 UTCEPSS rescore
  28. 2026-08-05 19:15 UTCEPSS rescore
  29. 2026-08-05 10:15 UTCEG score recompute
  30. 2026-08-05 10:15 UTCGHSA enrichment
  31. 2026-08-04 10:49 UTCEG score recompute
  32. 2026-08-04 10:48 UTCGHSA enrichment
  33. 2026-08-04 10:36 UTCEPSS rescore
  34. 2026-08-04 09:24 UTCEG score recompute▲ 9.80
  35. 2026-08-04 09:23 UTCGHSA enrichment
  36. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  37. 2026-08-03 10:34 UTCEPSS rescore
  38. 2026-08-02 02:25 UTCEPSS rescore
  39. 2026-08-02 02:25 UTCEPSS rescore
  40. 2026-08-01 04:14 UTCEPSS rescore
  41. 2026-07-30 16:26 UTCEPSS rescore
  42. 2026-07-30 01:29 UTCEPSS rescore
  43. 2026-07-28 15:34 UTCEPSS rescore
  44. 2026-07-28 15:34 UTCEPSS rescore
  45. 2026-07-27 03:39 UTCOSV refresh
  46. 2026-07-26 14:53 UTCEPSS rescore
  47. 2026-07-24 14:16 UTCEPSS rescore
  48. 2026-07-23 14:16 UTCEPSS rescore
  49. 2026-07-23 02:30 UTCEG score recompute
  50. 2026-07-22 23:16 UTCEG score recompute
  51. 2026-07-22 14:07 UTCEPSS rescore
  52. 2026-07-22 14:07 UTCEPSS rescore
  53. 2026-07-21 15:23 UTCEPSS rescore
  54. 2026-07-20 17:06 UTCEPSS rescore
  55. 2026-07-19 14:30 UTCEPSS rescore
  56. 2026-07-19 14:29 UTCEPSS rescore
  57. 2026-07-19 02:27 UTCEPSS rescore
  58. 2026-07-19 02:27 UTCEPSS rescore
  59. 2026-07-18 10:03 UTCEPSS rescore
  60. 2026-07-18 10:03 UTCEPSS rescore
  61. 2026-07-16 17:01 UTCEPSS rescore
  62. 2026-07-15 16:56 UTCEPSS rescore
  63. 2026-07-15 01:59 UTCEPSS rescore
  64. 2026-07-15 01:59 UTCEPSS rescore
  65. 2026-07-13 22:28 UTCEPSS rescore
  66. 2026-07-13 22:28 UTCEPSS rescore
  67. 2026-07-13 06:11 UTCEPSS rescore
  68. 2026-07-12 05:45 UTCEPSS rescore
  69. 2026-07-12 05:45 UTCEPSS rescore
  70. 2026-07-11 08:26 UTCEPSS rescore
  71. 2026-07-09 22:17 UTCOSV refresh
  72. 2026-07-09 19:08 UTCEPSS rescore
  73. 2026-07-08 15:13 UTCEPSS rescore
  74. 2026-07-07 13:45 UTCEPSS rescore
  75. 2026-07-07 13:44 UTCEPSS rescore

Related CVEs(same product)

Frequently asked(5)

What is CVE-2023-54094?
CVE-2023-54094 is a critical vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: net: prevent skb corruption on frag list segmentation Ian reported several skb corruptions triggered by rx-gro-list, collecting different oops alike: [ 62.624003] BUG: kernel NULL pointer dereference, address: 00000000000000c0 […
When was CVE-2023-54094 disclosed?
CVE-2023-54094 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54094 actively exploited?
CVE-2023-54094 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.7% of all scored CVEs.
What is the CVSS score of CVE-2023-54094?
CVE-2023-54094 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54094?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54094, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-54094

Explore →

Is Your Infrastructure Affected by CVE-2023-54094?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs