CVE-2023-53107

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-13153 (ENISA EUVD) · GHSA-wmmr-m98c-g94f (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

veth: Fix use after free in XDP_REDIRECT

Commit 718a18a0c8a6 ("veth: Rework veth_xdp_rcv_skb in order to accept non-linear skb") introduced a bug where it tried to use pskb_expand_head() if the headroom was less than XDP_PACKET_HEADROOM. This however uses kmalloc to expand the head, which will later allow consume_skb() to free the skb while is it still in use by AF_XDP.

Previously if the headroom was less than XDP_PACKET_HEADROOM we continued on to allocate a new skb from pages so this restores that behavior.

BUG: KASAN: use-after-free in __xsk_rcv+0x18d/0x2c0 Read of size 78 at addr ffff888976250154 by task napi/iconduit-g/148640

CPU: 5 PID: 148640 Comm: napi/iconduit-g Kdump: loaded Tainted: G O 6.1.4-cloudflare-kasan-2023.1.2 #1 Hardware name: Quanta Computer Inc. QuantaPlex T41S-2U/S2S-MB, BIOS S2S_3B10.03 06/21/2018 Call Trace: dump_stack_lvl+0x34/0x48 print_report+0x170/0x473 ? __xsk_rcv+0x18d/0x2c0 kasan_report+0xad/0x130 ? __xsk_rcv+0x18d/0x2c0 kasan_check_range+0x149/0x1a0 memcpy+0x20/0x60 __xsk_rcv+0x18d/0x2c0 __xsk_map_redirect+0x1f3/0x490 ? veth_xdp_rcv_skb+0x89c/0x1ba0 [veth] xdp_do_redirect+0x5ca/0xd60 veth_xdp_rcv_skb+0x935/0x1ba0 [veth] ? __netif_receive_skb_list_core+0x671/0x920 ? veth_xdp+0x670/0x670 [veth] veth_xdp_rcv+0x304/0xa20 [veth] ? do_xdp_generic+0x150/0x150 ? veth_xdp_rcv_one+0xde0/0xde0 [veth] ? _raw_spin_lock_bh+0xe0/0xe0 ? newidle_balance+0x887/0xe30 ? __perf_event_task_sched_in+0xdb/0x800 veth_poll+0x139/0x571 [veth] ? veth_xdp_rcv+0xa20/0xa20 [veth] ? _raw_spin_unlock+0x39/0x70 ? finish_task_switch.isra.0+0x17e/0x7d0 ? __switch_to+0x5cf/0x1070 ? __schedule+0x95b/0x2640 ? io_schedule_timeout+0x160/0x160 __napi_poll+0xa1/0x440 napi_threaded_poll+0x3d1/0x460 ? __napi_poll+0x440/0x440 ? __kthread_parkme+0xc6/0x1f0 ? __napi_poll+0x440/0x440 kthread+0x2a2/0x340 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30

Freed by task 148640: kasan_save_stack+0x23/0x50 kasan_set_track+0x21/0x30 kasan_save_free_info+0x2a/0x40 ____kasan_slab_free+0x169/0x1d0 slab_free_freelist_hook+0xd2/0x190 __kmem_cache_free+0x1a1/0x2f0 skb_release_data+0x449/0x600 consume_skb+0x9f/0x1c0 veth_xdp_rcv_skb+0x89c/0x1ba0 [veth] veth_xdp_rcv+0x304/0xa20 [veth] veth_poll+0x139/0x571 [veth] __napi_poll+0xa1/0x440 napi_threaded_poll+0x3d1/0x460 kthread+0x2a2/0x340 ret_from_fork+0x22/0x30

The buggy address belongs to the object at ffff888976250000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 340 bytes inside of 2048-byte region [ffff888976250000, ffff888976250800)

The buggy address belongs to the physical page: page:00000000ae18262a refcount:2 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x976250 head:00000000ae18262a order:3 compound_mapcount:0 compound_pincount:0 flags: 0x2ffff800010200(slab|head|node=0|zone=2|lastcpupid=0x1ffff) raw: 002ffff800010200 0000000000000000 dead000000000122 ffff88810004cf00 raw: 0000000000000000 0000000080080008 00000002ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888976250000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888976250080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > ffff888976250100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888976250180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888976250200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 2, 2025

Last Modified

October 15, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
Patch available.
Web page

veth: Fix use after free in XDP_REDIRECT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c10131803e45269ddc6c817f19ed649110f3cae
Web page

veth: Fix use after free in XDP_REDIRECT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e755b56896df48b0fae0db275e148f8d8aa7d6f
Web page

veth: Fix use after free in XDP_REDIRECT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/717d20710596b5b26595ede454d1105fa176f4a4

Vendor Advisories for CVE-2023-53107(4)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkpatch-patch2025-06-02redhat
redhatkernel-0:5.14.0-284.118.1.el9_22025-05-26redhat
redhatkernel-rt-0:5.14.0-284.118.1.rt14.403.el9_22025-05-26redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.1.21 (fixes >=5.18.0)—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 rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 211 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53107?
CVE-2023-53107 is a high-severity vulnerability; its CVE record was published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: veth: Fix use after free in XDP_REDIRECT Commit 718a18a0c8a6 ("veth: Rework veth_xdp_rcv_skb in order to accept non-linear skb") introduced a bug where it tried to use pskb_expand_head() if the headroom was less than…
When was the CVE record for CVE-2023-53107 published?
The CVE record for CVE-2023-53107 was published on May 2, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2023-53107 actively exploited?
CVE-2023-53107 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53107?
CVE-2023-53107 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53107?
A fix for CVE-2023-53107 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53107 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-53107?

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

Book a Demo →Browse All CVEs