CVE-2023-53192: vxlan: Fix nexthop hash size
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0756384fb1bd38adb2ebcfd1307422f433a1d772, 23c195ce6f4aec86e1c9e1ea1c800381c4b465c7, 32ef2c0c6cf11a076f0280a7866b9abc47821e19.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.
Low priority for now. Upgrade to Linux Linux 0756384fb1bd38adb2ebcfd1307422f433a1d772, 23c195ce6f4aec86e1c9e1ea1c800381c4b465c7, 32ef2c0c6cf11a076f0280a7866b9abc47821e19 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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: <TASK> ? __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---
- Published
- Sep 15, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-129
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 9.8
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.8 and later · before 5.10.190
- linux linux kernel5.11 and later · before 5.15.126
- linux linux kernel5.16 and later · before 6.1.45
- linux linux kernel6.2 and later · before 6.4.10
- linux linux kernel6.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.8affected
- 1274e1cc42264d4e629841e4f182795cb0becfd2 and later · before c650597647ecb318d02372277bdfd866c6829f78affected · git
- 1274e1cc42264d4e629841e4f182795cb0becfd2 and later · before 32ef2c0c6cf11a076f0280a7866b9abc47821e19affected · git
- 1274e1cc42264d4e629841e4f182795cb0becfd2 and later · before 7b8717658dff8b471cbfc124bf9b5ca4229579edaffected · git
- 1274e1cc42264d4e629841e4f182795cb0becfd2 and later · before 23c195ce6f4aec86e1c9e1ea1c800381c4b465c7affected · git
- 1274e1cc42264d4e629841e4f182795cb0becfd2 and later · before 0756384fb1bd38adb2ebcfd1307422f433a1d772affected · git
- before 5.8not affected · semver
- 5.10.190 and later · up to and including 5.10.*not affected · semver
- 5.15.126 and later · up to and including 5.15.*not affected · semver
- 6.1.45 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.11-1 | 6.4.11-1 |
| Red Hat:rhel_e4s:9.0::appstream | bpftool-debuginfo | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-debuginfo | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-devel | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-devel-matched | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-devel | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-devel-matched | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-doc | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-tools-debuginfo | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-devel | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | perf | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | perf-debuginfo | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | python3-perf-debuginfo | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | bpftool | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | kernel | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | kernel-abi-stablelists | before 0:5.14.0-70.165.1.el9_0 | 0:5.14.0-70.165.1.el9_0 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53190Sep 15, 2025 · vxlan: Fix memory leaks in error path22Monitor
- ← EarlierCVE-2023-53191Sep 15, 2025 · irqchip/alpine-msi: Fix refcount leak in alpine_msix_init_domains22Monitor
- Later →CVE-2023-53193Sep 15, 2025 · drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v10_0_hw_fini22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0756384fb1bd38adb2ebcfd1307422f433a1d772 | Vendor (CNA) |
| Linux Linux | 23c195ce6f4aec86e1c9e1ea1c800381c4b465c7 | Vendor (CNA) |
| Linux Linux | 32ef2c0c6cf11a076f0280a7866b9abc47821e19 | Vendor (CNA) |
| Linux Linux | 7b8717658dff8b471cbfc124bf9b5ca4229579ed | Vendor (CNA) |
| Linux Linux | c650597647ecb318d02372277bdfd866c6829f78 | Vendor (CNA) |
| debian:linux | 6.1.52-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-s390x | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-x86_64 | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-devel | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-devel-matched | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-doc | 0:5.14.0-70.165.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2021-47548479 days apartethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()39Monitor
- CVE-2026-64018307 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access37Monitor
- CVE-2026-23246184 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration35Monitor
- CVE-2026-43110233 days apartwifi: brcmfmac: validate bsscfg indices in IF events35Monitor
- CVE-2026-43172233 days apartwifi: iwlwifi: fix 22000 series SMEM parsing35Monitor
- CVE-2022-503150 days apartata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.