CVE-2023-52435

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-02-20. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-57060 (ENISA EUVD) · GHSA-6vr7-3j3q-8546 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: prevent mss overflow in skb_segment()

Once again syzbot is able to crash the kernel in skb_segment() [1]

GSO_BY_FRAGS is a forbidden value, but unfortunately the following computation in skb_segment() can reach it quite easily :

mss = mss * partial_segs;

65535 = 3 * 5 * 17 * 257, so many initial values of mss can lead to a bad final result.

Make sure to limit segmentation so that the new mss value is smaller than GSO_BY_FRAGS.

[1]

general protection fault, probably for non-canonical address 0xdffffc000000000e: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077] CPU: 1 PID: 5079 Comm: syz-executor993 Not tainted 6.7.0-rc4-syzkaller-00141-g1ae4cd3cbdd0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023 RIP: 0010:skb_segment+0x181d/0x3f30 net/core/skbuff.c:4551 Code: 83 e3 02 e9 fb ed ff ff e8 90 68 1c f9 48 8b 84 24 f8 00 00 00 48 8d 78 70 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e 8a 21 00 00 48 8b 84 24 f8 00 RSP: 0018:ffffc900043473d0 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000010046 RCX: ffffffff886b1597 RDX: 000000000000000e RSI: ffffffff886b2520 RDI: 0000000000000070 RBP: ffffc90004347578 R08: 0000000000000005 R09: 000000000000ffff R10: 000000000000ffff R11: 0000000000000002 R12: ffff888063202ac0 R13: 0000000000010000 R14: 000000000000ffff R15: 0000000000000046 FS: 0000555556e7e380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020010000 CR3: 0000000027ee2000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:

udp6_ufo_fragment+0xa0e/0xd00 net/ipv6/udp_offload.c:109 ipv6_gso_segment+0x534/0x17e0 net/ipv6/ip6_offload.c:120 skb_mac_gso_segment+0x290/0x610 net/core/gso.c:53 __skb_gso_segment+0x339/0x710 net/core/gso.c:124 skb_gso_segment include/net/gso.h:83 [inline] validate_xmit_skb+0x36c/0xeb0 net/core/dev.c:3626 __dev_queue_xmit+0x6f3/0x3d60 net/core/dev.c:4338 dev_queue_xmit include/linux/netdevice.h:3134 [inline] packet_xmit+0x257/0x380 net/packet/af_packet.c:276 packet_snd net/packet/af_packet.c:3087 [inline] packet_sendmsg+0x24c6/0x5220 net/packet/af_packet.c:3119 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0xd5/0x180 net/socket.c:745 __sys_sendto+0x255/0x340 net/socket.c:2190 __do_sys_sendto net/socket.c:2202 [inline] __se_sys_sendto net/socket.c:2198 [inline] __x64_sys_sendto+0xe0/0x1b0 net/socket.c:2198 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7f8692032aa9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 d1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff8d685418 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f8692032aa9 RDX: 0000000000010048 RSI: 00000000200000c0 RDI: 0000000000000003 RBP: 00000000000f4240 R08: 0000000020000540 R09: 0000000000000014 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff8d685480 R13: 0000000000000001 R14: 00007fff8d685480 R15: 0000000000000003

Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:skb_segment+0x181d/0x3f30 net/core/skbuff.c:4551 Code: 83 e3 02 e9 fb ed ff ff e8 90 68 1c f9 48 8b 84 24 f8 00 00 00 48 8d 78 70 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e 8a 21 00 00 48 8b 84 24 f8 00 RSP: 0018:ffffc900043473d0 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000010046 RCX: ffffffff886b1597 RDX: 000000000000000e RSI: ffffffff886b2520 RDI: 0000000000000070 RBP: ffffc90004347578 R0 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
14th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-25). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

February 20, 2024

Last Modified

November 21, 2024

Vendor Advisories for CVE-2023-52435(1)

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

Patch Availability(13)

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

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)
  • every version up to 5.10.216-1~deb10u1: fixed in 5.10.216-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)
  • every version up to 6.1.82-1: fixed in 6.1.82-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.11-1: fixed in 6.6.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.11-1: fixed in 6.6.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 93 of 201 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 108 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% · 14th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-25 17:29 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-24 11:44 UTCEG score recompute
  13. 2026-10-24 11:44 UTCVendor advisory
  14. 2026-10-24 11:44 UTCGHSA enrichmentGHSA-6vr7-3j3q-8546 · GitHub CVSS 5.5
  15. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-10-18 07:42 UTCEG score recompute
  22. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 68 more
  1. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-12 18:13 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-11 23:54 UTCOSV refresh
  5. 2026-10-11 21:38 UTCEG score recompute
  6. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-09-30 16:36 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-09-22 07:46 UTCOSV refresh
  24. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  28. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  30. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  32. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  33. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  34. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  35. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  36. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  37. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  38. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  39. 2026-09-03 04:59 UTCOSV refresh
  40. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  41. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  42. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  43. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  44. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  45. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  46. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  47. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  49. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-16 18:26 UTCOSV refresh
  54. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  61. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  62. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  63. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  64. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  65. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  66. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  67. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile

Frequently asked(5)

What is CVE-2023-52435?
CVE-2023-52435 is a medium-severity vulnerability; its CVE record was published on February 20, 2024. In the Linux kernel, the following vulnerability has been resolved: net: prevent mss overflow in skb_segment() Once again syzbot is able to crash the kernel in skb_segment() [1] GSO_BY_FRAGS is a forbidden value, but unfortunately the following computation in skb_segment() can reach it quite easily…
When was the CVE record for CVE-2023-52435 published?
The CVE record for CVE-2023-52435 was published on February 20, 2024. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-52435 actively exploited?
CVE-2023-52435 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52435?
CVE-2023-52435 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52435?
A fix for CVE-2023-52435 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52435 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-52435

Explore →

Is Your Infrastructure Affected by CVE-2023-52435?

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