CVE-2023-52610

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-03-18. 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: 1%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

net/sched: act_ct: fix skb leak and crash on ooo frags

act_ct adds skb->users before defragmentation. If frags arrive in order, the last frag's reference is reset in:

inet_frag_reasm_prepare skb_morph

which is not straightforward.

However when frags arrive out of order, nobody unref the last frag, and all frags are leaked. The situation is even worse, as initiating packet capture can lead to a crash[0] when skb has been cloned and shared at the same time.

Fix the issue by removing skb_get() before defragmentation. act_ct returns TC_ACT_CONSUMED when defrag failed or in progress.

[0]: [ 843.804823] ------------[ cut here ]------------ [ 843.809659] kernel BUG at net/core/skbuff.c:2091! [ 843.814516] invalid opcode: 0000 [#1] PREEMPT SMP [ 843.819296] CPU: 7 PID: 0 Comm: swapper/7 Kdump: loaded Tainted: G S 6.7.0-rc3 #2 [ 843.824107] Hardware name: XFUSION 1288H V6/BC13MBSBD, BIOS 1.29 11/25/2022 [ 843.828953] RIP: 0010:pskb_expand_head+0x2ac/0x300 [ 843.833805] Code: 8b 70 28 48 85 f6 74 82 48 83 c6 08 bf 01 00 00 00 e8 38 bd ff ff 8b 83 c0 00 00 00 48 03 83 c8 00 00 00 e9 62 ff ff ff 0f 0b <0f> 0b e8 8d d0 ff ff e9 b3 fd ff ff 81 7c 24 14 40 01 00 00 4c 89 [ 843.843698] RSP: 0018:ffffc9000cce07c0 EFLAGS: 00010202 [ 843.848524] RAX: 0000000000000002 RBX: ffff88811a211d00 RCX: 0000000000000820 [ 843.853299] RDX: 0000000000000640 RSI: 0000000000000000 RDI: ffff88811a211d00 [ 843.857974] RBP: ffff888127d39518 R08: 00000000bee97314 R09: 0000000000000000 [ 843.862584] R10: 0000000000000000 R11: ffff8881109f0000 R12: 0000000000000880 [ 843.867147] R13: ffff888127d39580 R14: 0000000000000640 R15: ffff888170f7b900 [ 843.871680] FS: 0000000000000000(0000) GS:ffff889ffffc0000(0000) knlGS:0000000000000000 [ 843.876242] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 843.880778] CR2: 00007fa42affcfb8 CR3: 000000011433a002 CR4: 0000000000770ef0 [ 843.885336] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 843.889809] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 843.894229] PKRU: 55555554 [ 843.898539] Call Trace: [ 843.902772] [ 843.906922] ? __die_body+0x1e/0x60 [ 843.911032] ? die+0x3c/0x60 [ 843.915037] ? do_trap+0xe2/0x110 [ 843.918911] ? pskb_expand_head+0x2ac/0x300 [ 843.922687] ? do_error_trap+0x65/0x80 [ 843.926342] ? pskb_expand_head+0x2ac/0x300 [ 843.929905] ? exc_invalid_op+0x50/0x60 [ 843.933398] ? pskb_expand_head+0x2ac/0x300 [ 843.936835] ? asm_exc_invalid_op+0x1a/0x20 [ 843.940226] ? pskb_expand_head+0x2ac/0x300 [ 843.943580] inet_frag_reasm_prepare+0xd1/0x240 [ 843.946904] ip_defrag+0x5d4/0x870 [ 843.950132] nf_ct_handle_fragments+0xec/0x130 [nf_conntrack] [ 843.953334] tcf_ct_act+0x252/0xd90 [act_ct] [ 843.956473] ? tcf_mirred_act+0x516/0x5a0 [act_mirred] [ 843.959657] tcf_action_exec+0xa1/0x160 [ 843.962823] fl_classify+0x1db/0x1f0 [cls_flower] [ 843.966010] ? skb_clone+0x53/0xc0 [ 843.969173] tcf_classify+0x24d/0x420 [ 843.972333] tc_run+0x8f/0xf0 [ 843.975465] __netif_receive_skb_core+0x67a/0x1080 [ 843.978634] ? dev_gro_receive+0x249/0x730 [ 843.981759] __netif_receive_skb_list_core+0x12d/0x260 [ 843.984869] netif_receive_skb_list_internal+0x1cb/0x2f0 [ 843.987957] ? mlx5e_handle_rx_cqe_mpwrq_rep+0xfa/0x1a0 [mlx5_core] [ 843.991170] napi_complete_done+0x72/0x1a0 [ 843.994305] mlx5e_napi_poll+0x28c/0x6d0 [mlx5_core] [ 843.997501] __napi_poll+0x25/0x1b0 [ 844.000627] net_rx_action+0x256/0x330 [ 844.003705] __do_softirq+0xb3/0x29b [ 844.006718] irq_exit_rcu+0x9e/0xc0 [ 844.009672] common_interrupt+0x86/0xa0 [ 844.012537] [ 844.015285] [ 844.017937] asm_common_interrupt+0x26/0x40 [ 844.020591] RIP: 0010:acpi_safe_halt+0x1b/0x20 [ 844.023247] Code: ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 65 48 8b 04 25 00 18 03 00 48 8b 00 a8 08 75 0c 66 90 0f 00 2d 81 d0 44 00 fb ---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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

March 18, 2024

Last Modified

August 5, 2026

References (5)

Vendor Advisories for CVE-2023-52610(9)

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

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.41.41) @ mantic2026-05-24ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1024.26) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.41.41~22.04.2) @ jammy2026-05-24ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1017.20) @ mantic2026-05-24ubuntu
ubuntulinux-tools-starfive (6.5.0.1015.17) @ mantic2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.24~22.04.1) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.26) @ mantic2026-05-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.5.0.1021.29) @ jammy2026-05-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1057.58) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.102.99) @ jammy2026-05-24ubuntu
redhatkernel-0:5.14.0-70.157.1.el9_02025-12-10redhat
redhatkernel-rt-0:5.14.0-70.157.1.rt21.229.el9_02025-12-10redhat
redhatkernel-rt-0:5.14.0-284.148.1.rt14.433.el9_22025-11-25redhat
redhatkernel-0:5.14.0-284.148.1.el9_22025-11-25redhat
redhatkernel-0:4.18.0-372.119.1.el8_62024-08-21redhat
redhatkernel-0:4.18.0-477.67.1.el8_82024-08-13redhat
redhatkernel-0:4.18.0-553.5.1.el8_102024-06-05redhat
redhatkernel-rt-0:4.18.0-553.5.1.rt7.346.el8_102024-06-05redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.15.148—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 ... 7.2~rc5-1~exp1 (498 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (17 versions)6.1.76-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.6.15-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.6.15-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

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 154 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:24 UTCEG score recompute
  12. 2026-08-05 10:24 UTCVendor advisory
  13. 2026-08-05 10:24 UTCGHSA enrichment
  14. 2026-08-04 12:20 UTCEG score recompute
  15. 2026-08-04 12:20 UTCVendor advisory
  16. 2026-08-04 12:20 UTCGHSA enrichment
  17. 2026-08-04 10:36 UTCEPSS rescore
  18. 2026-08-04 09:53 UTCEG score recompute
  19. 2026-08-04 09:53 UTCVendor advisory
  20. 2026-08-04 09:53 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 09:36 UTCOSV refresh
  25. 2026-08-01 04:14 UTCEPSS rescore
  26. 2026-07-30 16:26 UTCEPSS rescore
  27. 2026-07-30 01:29 UTCEPSS rescore
  28. 2026-07-28 15:34 UTCEPSS rescore
  29. 2026-07-28 15:34 UTCEPSS rescore
  30. 2026-07-26 14:53 UTCEPSS rescore
  31. 2026-07-25 14:16 UTCEPSS rescore
  32. 2026-07-24 14:16 UTCEPSS rescore
  33. 2026-07-23 14:16 UTCEPSS rescore
  34. 2026-07-23 02:29 UTCEG score recompute
  35. 2026-07-22 23:15 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-18 10:03 UTCEPSS rescore
  45. 2026-07-18 10:03 UTCEPSS rescore
  46. 2026-07-16 17:01 UTCEPSS rescore
  47. 2026-07-15 16:56 UTCEPSS rescore
  48. 2026-07-15 01:59 UTCEPSS rescore
  49. 2026-07-15 01:59 UTCEPSS rescore
  50. 2026-07-14 16:55 UTCOSV refresh
  51. 2026-07-13 22:28 UTCEPSS rescore
  52. 2026-07-13 22:28 UTCEPSS rescore
  53. 2026-07-13 06:11 UTCEPSS rescore
  54. 2026-07-12 05:45 UTCEPSS rescore
  55. 2026-07-12 05:45 UTCEPSS rescore
  56. 2026-07-11 08:26 UTCEPSS rescore
  57. 2026-07-09 19:08 UTCEPSS rescore
  58. 2026-07-08 15:13 UTCEPSS rescore
  59. 2026-07-07 13:45 UTCEPSS rescore
  60. 2026-07-07 13:44 UTCEPSS rescore
  61. 2026-07-06 16:26 UTCEPSS rescore
  62. 2026-07-06 16:26 UTCEPSS rescore
  63. 2026-07-06 02:22 UTCEPSS rescore
  64. 2026-07-06 02:22 UTCEPSS rescore
  65. 2026-07-05 02:29 UTCEPSS rescore
  66. 2026-07-04 06:29 UTCEPSS rescore
  67. 2026-07-01 15:05 UTCEPSS rescore
  68. 2026-06-29 14:05 UTCEPSS rescore
  69. 2026-06-28 14:06 UTCEPSS rescore
  70. 2026-06-28 14:06 UTCEPSS rescore
  71. 2026-06-28 04:55 UTCEPSS rescore
  72. 2026-06-27 03:07 UTCEPSS rescore
  73. 2026-06-26 17:39 UTCOSV refresh
  74. 2026-06-25 13:48 UTCEPSS rescore
  75. 2026-06-25 13:48 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-52610?
CVE-2023-52610 is a medium vulnerability published on March 18, 2024. In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: fix skb leak and crash on ooo frags act_ct adds skb->users before defragmentation. If frags arrive in order, the last frag's reference is reset in: inetfragreasm_prepare skb_morph which is not straightforward.…
When was CVE-2023-52610 disclosed?
CVE-2023-52610 was first published in the National Vulnerability Database on March 18, 2024, 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-52610 actively exploited?
CVE-2023-52610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.6% of all scored CVEs.
What is the CVSS score of CVE-2023-52610?
CVE-2023-52610 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52610, 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-52610

Explore →

Is Your Infrastructure Affected by CVE-2023-52610?

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

Start Free Scan →Browse All CVEs