CVE-2023-53110

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-05-02. 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/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler()

When performing a stress test on SMC-R by rmmod mlx5_ib driver during the wrk/nginx test, we found that there is a probability of triggering a panic while terminating all link groups.

This issue dues to the race between smc_smcr_terminate_all() and smc_buf_create().

smc_smcr_terminate_all

smc_buf_create /* init */ conn->sndbuf_desc = NULL; ...

__smc_lgr_terminate smc_conn_kill smc_close_abort smc_cdc_get_slot_and_msg_send

__softirqentry_text_start smc_wr_tx_process_cqe smc_cdc_tx_handler READ(conn->sndbuf_desc->len); /* panic dues to NULL sndbuf_desc */

conn->sndbuf_desc = xxx;

This patch tries to fix the issue by always to check the sndbuf_desc before send any cdc msg, to make sure that no null pointer is seen during cqe processing.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

May 2, 2025

Last Modified

August 5, 2026

Vendor Advisories for CVE-2023-53110(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.10.176osv

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 ... 5.10.92-2 (25 versions)5.10.178-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.25-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.1.25-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.1.25-1

Weakness Classification(1)

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

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 151 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-53110?
CVE-2023-53110 is a medium vulnerability published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: net/smc: fix NULL sndbufdesc in smccdctxhandler() When performing a stress test on SMC-R by rmmod mlx5_ib driver during the wrk/nginx test, we found that there is a probability of triggering a panic while terminating all link…
When was CVE-2023-53110 disclosed?
CVE-2023-53110 was first published in the National Vulnerability Database on May 2, 2025, 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-53110 actively exploited?
CVE-2023-53110 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 61.1% of all scored CVEs.
What is the CVSS score of CVE-2023-53110?
CVE-2023-53110 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53110?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53110, 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-53110

Explore →

Is Your Infrastructure Affected by CVE-2023-53110?

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