CVE-2023-54166

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

igc: Fix Kernel Panic during ndo_tx_timeout callback

The Xeon validation group has been carrying out some loaded tests with various HW configurations, and they have seen some transmit queue time out happening during the test. This will cause the reset adapter function to be called by igc_tx_timeout(). Similar race conditions may arise when the interface is being brought down and up in igc_reinit_locked(), an interrupt being generated, and igc_clean_tx_irq() being called to complete the TX.

When the igc_tx_timeout() function is invoked, this patch will turn off all TX ring HW queues during igc_down() process. TX ring HW queues will be activated again during the igc_configure_tx_ring() process when performing the igc_up() procedure later.

This patch also moved existing igc_disable_tx_ring_hw() to avoid using forward declaration.

Kernel trace: [ 7678.747813] ------------[ cut here ]------------ [ 7678.757914] NETDEV WATCHDOG: enp1s0 (igc): transmit queue 2 timed out [ 7678.770117] WARNING: CPU: 0 PID: 13 at net/sched/sch_generic.c:525 dev_watchdog+0x1ae/0x1f0 [ 7678.784459] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc overlay dm_mod emrcha(PO) emriio(PO) rktpm(PO) cegbuf_mod(PO) patch_update(PO) se(PO) sgx_tgts(PO) mktme(PO) keylocker(PO) svtdx(PO) svfs_pci_hotplug(PO) vtd_mod(PO) davemem(PO) svmabort(PO) svindexio(PO) usbx2(PO) ehci_sched(PO) svheartbeat(PO) ioapic(PO) sv8259(PO) svintr(PO) lt(PO) pcierootport(PO) enginefw_mod(PO) ata(PO) smbus(PO) spiflash_cdf(PO) arden(PO) dsa_iax(PO) oobmsm_punit(PO) cpm(PO) svkdb(PO) ebg_pch(PO) pch(PO) sviotargets(PO) svbdf(PO) svmem(PO) svbios(PO) dram(PO) svtsc(PO) targets(PO) superio(PO) svkernel(PO) cswitch(PO) mcf(PO) pentiumIII_mod(PO) fs_svfs(PO) mdevdefdb(PO) svfs_os_services(O) ixgbe mdio mdio_devres libphy emeraldrapids_svdefs(PO) regsupport(O) libnvdimm nls_cp437 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hwdep x86_pkg_temp_thermal snd_hda_core snd_pcm snd_timer isst_if_mbox_pci [ 7678.784496] input_leds isst_if_mmio sg snd isst_if_common soundcore wmi button sad9(O) drm fuse backlight configfs efivarfs ip_tables x_tables vmd sdhci led_class rtl8150 r8152 hid_generic pegasus mmc_block usbhid mmc_core hid megaraid_sas ixgb igb i2c_algo_bit ice i40e hpsa scsi_transport_sas e1000e e1000 e100 ax88179_178a usbnet xhci_pci sd_mod xhci_hcd t10_pi crc32c_intel crc64_rocksoft igc crc64 crc_t10dif usbcore crct10dif_generic ptp crct10dif_common usb_common pps_core [ 7679.200403] RIP: 0010:dev_watchdog+0x1ae/0x1f0 [ 7679.210201] Code: 28 e9 53 ff ff ff 4c 89 e7 c6 05 06 42 b9 00 01 e8 17 d1 fb ff 44 89 e9 4c 89 e6 48 c7 c7 40 ad fb 81 48 89 c2 e8 52 62 82 ff <0f> 0b e9 72 ff ff ff 65 8b 05 80 7d 7c 7e 89 c0 48 0f a3 05 0a c1 [ 7679.245438] RSP: 0018:ffa00000001f7d90 EFLAGS: 00010282 [ 7679.256021] RAX: 0000000000000000 RBX: ff11000109938440 RCX: 0000000000000000 [ 7679.268710] RDX: ff11000361e26cd8 RSI: ff11000361e1b880 RDI: ff11000361e1b880 [ 7679.281314] RBP: ffa00000001f7da8 R08: ff1100035f8fffe8 R09: 0000000000027ffb [ 7679.293840] R10: 0000000000001f0a R11: ff1100035f840000 R12: ff11000109938000 [ 7679.306276] R13: 0000000000000002 R14: dead000000000122 R15: ffa00000001f7e18 [ 7679.318648] FS: 0000000000000000(0000) GS:ff11000361e00000(0000) knlGS:0000000000000000 [ 7679.332064] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7679.342757] CR2: 00007ffff7fca168 CR3: 000000013b08a006 CR4: 0000000000471ef8 [ 7679.354984] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 7679.367207] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [ 7679.379370] PKRU: 55555554 [ 7679.386446] Call Trace: [ 7679.393152] [ 7679.399363] ? __pfx_dev_watchdog+0x10/0x10 [ 7679.407870] call_timer_fn+0x31/0x110 [ 7679.415698] e ---truncated---

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

December 30, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

igc: Fix Kernel Panic during ndo_tx_timeout callback - kernel/git/stable/linux.git - Linux kernel stable tree

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

igc: Fix Kernel Panic during ndo_tx_timeout callback - kernel/git/stable/linux.git - Linux kernel stable tree

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

igc: Fix Kernel Panic during ndo_tx_timeout callback - kernel/git/stable/linux.git - Linux kernel stable tree

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

igc: Fix Kernel Panic during ndo_tx_timeout callback - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2023-54166(3)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.15.124—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

(3 across 3 ecosystems)
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 / 27× 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 192 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-54166?
CVE-2023-54166 is a high vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: igc: Fix Kernel Panic during ndotxtimeout callback The Xeon validation group has been carrying out some loaded tests with various HW configurations, and they have seen some transmit queue time out happening during the test. This…
When was CVE-2023-54166 disclosed?
CVE-2023-54166 was first published in the National Vulnerability Database on December 30, 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-54166 actively exploited?
CVE-2023-54166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.5% of all scored CVEs.
What is the CVSS score of CVE-2023-54166?
CVE-2023-54166 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54166?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54166, 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-54166

Explore →

Is Your Infrastructure Affected by CVE-2023-54166?

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

Start Free Scan →Browse All CVEs