CVE-2023-53192

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

vxlan: Fix nexthop hash size

The nexthop code expects a 31 bit hash, such as what is returned by fib_multipath_hash() and rt6_multipath_hash(). Passing the 32 bit hash returned by skb_get_hash() can lead to problems related to the fact that 'int hash' is a negative number when the MSB is set.

In the case of hash threshold nexthop groups, nexthop_select_path_hthr() will disproportionately select the first nexthop group entry. In the case of resilient nexthop groups, nexthop_select_path_res() may do an out of bounds access in nh_buckets[], for example: hash = -912054133 num_nh_buckets = 2 bucket_index = 65535

which leads to the following panic:

BUG: unable to handle page fault for address: ffffc900025910c8 PGD 100000067 P4D 100000067 PUD 10026b067 PMD 0 Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI CPU: 4 PID: 856 Comm: kworker/4:3 Not tainted 6.5.0-rc2+ #34 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:nexthop_select_path+0x197/0xbf0 Code: c1 e4 05 be 08 00 00 00 4c 8b 35 a4 14 7e 01 4e 8d 6c 25 00 4a 8d 7c 25 08 48 01 dd e8 c2 25 15 ff 49 8d 7d 08 e8 39 13 15 ff <4d> 89 75 08 48 89 ef e8 7d 12 15 ff 48 8b 5d 00 e8 14 55 2f 00 85 RSP: 0018:ffff88810c36f260 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 00000000002000c0 RCX: ffffffffaf02dd77 RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffffc900025910c8 RBP: ffffc900025910c0 R08: 0000000000000001 R09: fffff520004b2219 R10: ffffc900025910cf R11: 31392d2068736168 R12: 00000000002000c0 R13: ffffc900025910c0 R14: 00000000fffef608 R15: ffff88811840e900 FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc900025910c8 CR3: 0000000129d00000 CR4: 0000000000750ee0 PKRU: 55555554 Call Trace: ? __die+0x23/0x70 ? page_fault_oops+0x1ee/0x5c0 ? __pfx_is_prefetch.constprop.0+0x10/0x10 ? __pfx_page_fault_oops+0x10/0x10 ? search_bpf_extables+0xfe/0x1c0 ? fixup_exception+0x3b/0x470 ? exc_page_fault+0xf6/0x110 ? asm_exc_page_fault+0x26/0x30 ? nexthop_select_path+0x197/0xbf0 ? nexthop_select_path+0x197/0xbf0 ? lock_is_held_type+0xe7/0x140 vxlan_xmit+0x5b2/0x2340 ? __lock_acquire+0x92b/0x3370 ? __pfx_vxlan_xmit+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_register_lock_class+0x10/0x10 ? skb_network_protocol+0xce/0x2d0 ? dev_hard_start_xmit+0xca/0x350 ? __pfx_vxlan_xmit+0x10/0x10 dev_hard_start_xmit+0xca/0x350 __dev_queue_xmit+0x513/0x1e20 ? __pfx___dev_queue_xmit+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? mark_held_locks+0x44/0x90 ? skb_push+0x4c/0x80 ? eth_header+0x81/0xe0 ? __pfx_eth_header+0x10/0x10 ? neigh_resolve_output+0x215/0x310 ? ip6_finish_output2+0x2ba/0xc90 ip6_finish_output2+0x2ba/0xc90 ? lock_release+0x236/0x3e0 ? ip6_mtu+0xbb/0x240 ? __pfx_ip6_finish_output2+0x10/0x10 ? find_held_lock+0x83/0xa0 ? lock_is_held_type+0xe7/0x140 ip6_finish_output+0x1ee/0x780 ip6_output+0x138/0x460 ? __pfx_ip6_output+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_ip6_finish_output+0x10/0x10 NF_HOOK.constprop.0+0xc0/0x420 ? __pfx_NF_HOOK.constprop.0+0x10/0x10 ? ndisc_send_skb+0x2c0/0x960 ? __pfx_lock_release+0x10/0x10 ? __local_bh_enable_ip+0x93/0x110 ? lock_is_held_type+0xe7/0x140 ndisc_send_skb+0x4be/0x960 ? __pfx_ndisc_send_skb+0x10/0x10 ? mark_held_locks+0x65/0x90 ? find_held_lock+0x83/0xa0 ndisc_send_ns+0xb0/0x110 ? __pfx_ndisc_send_ns+0x10/0x10 addrconf_dad_work+0x631/0x8e0 ? lock_acquire+0x180/0x3f0 ? __pfx_addrconf_dad_work+0x10/0x10 ? mark_held_locks+0x24/0x90 process_one_work+0x582/0x9c0 ? __pfx_process_one_work+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? mark_held_locks+0x24/0x90 worker_thread+0x93/0x630 ? __kthread_parkme+0xdc/0x100 ? __pfx_worker_thread+0x10/0x10 kthread+0x1a5/0x1e0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x60 ---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
31%
KEV
Not listed

Published

September 15, 2025

Last Modified

August 5, 2026

Advisory Details (5)

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

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0756384fb1bd38adb2ebcfd1307422f433a1d772
generic

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23c195ce6f4aec86e1c9e1ea1c800381c4b465c7
generic

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32ef2c0c6cf11a076f0280a7866b9abc47821e19
generic

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2023-53192(5)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:5.14.0-284.158.1.rt14.443.el9_22026-02-25redhat
redhatkernel-0:5.14.0-284.158.1.el9_22026-02-25redhat
redhatkernel-0:5.14.0-70.165.1.el9_02026-02-11redhat
redhatkernel-rt-0:5.14.0-70.165.1.rt21.237.el9_02026-02-11redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.10.190—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—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× 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 145 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53192?
CVE-2023-53192 is a high vulnerability published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix nexthop hash size The nexthop code expects a 31 bit hash, such as what is returned by fibmultipathhash() and rt6multipathhash(). Passing the 32 bit hash returned by skbgethash() can lead to problems related to the fact…
When was CVE-2023-53192 disclosed?
CVE-2023-53192 was first published in the National Vulnerability Database on September 15, 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-53192 actively exploited?
CVE-2023-53192 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 68.8% of all scored CVEs.
What is the CVSS score of CVE-2023-53192?
CVE-2023-53192 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53192?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53192, 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-53192

Explore →

Is Your Infrastructure Affected by CVE-2023-53192?

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

Start Free Scan →Browse All CVEs