CVE-2023-52435

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

February 20, 2024

Last Modified

November 21, 2024

References (14)

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 rangeFixed inDependents
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)5.10.216-1~deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)5.10.216-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)6.1.82-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.6.11-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.6.11-1—

Weakness Classification(1)

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

All Vendor Advisories

(13)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2023-52435?
CVE-2023-52435 is a medium vulnerability 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] GSOBYFRAGS is a forbidden value, but unfortunately the following computation in skb_segment() can reach it quite easily :…
When was CVE-2023-52435 disclosed?
CVE-2023-52435 was first published in the National Vulnerability Database on February 20, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-52435 actively exploited?
CVE-2023-52435 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 87.6% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52435, 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-52435

Explore →

Is Your Infrastructure Affected by CVE-2023-52435?

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