CVE-2023-54237

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-30. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link()

There is a certain chance to trigger the following panic:

PID: 5900 TASK: ffff88c1c8af4100 CPU: 1 COMMAND: "kworker/1:48" #0 [ffff9456c1cc79a0] machine_kexec at ffffffff870665b7 #1 [ffff9456c1cc79f0] __crash_kexec at ffffffff871b4c7a #2 [ffff9456c1cc7ab0] crash_kexec at ffffffff871b5b60 #3 [ffff9456c1cc7ac0] oops_end at ffffffff87026ce7 #4 [ffff9456c1cc7ae0] page_fault_oops at ffffffff87075715 #5 [ffff9456c1cc7b58] exc_page_fault at ffffffff87ad0654 #6 [ffff9456c1cc7b80] asm_exc_page_fault at ffffffff87c00b62 [exception RIP: ib_alloc_mr+19] RIP: ffffffffc0c9cce3 RSP: ffff9456c1cc7c38 RFLAGS: 00010202 RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000004 RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffff88c1ea281d00 R8: 000000020a34ffff R9: ffff88c1350bbb20 R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000 R13: 0000000000000010 R14: ffff88c1ab040a50 R15: ffff88c1ea281d00 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffff9456c1cc7c60] smc_ib_get_memory_region at ffffffffc0aff6df [smc] #8 [ffff9456c1cc7c88] smcr_buf_map_link at ffffffffc0b0278c [smc] #9 [ffff9456c1cc7ce0] __smc_buf_create at ffffffffc0b03586 [smc]

The reason here is that when the server tries to create a second link, smc_llc_srv_add_link() has no protection and may add a new link to link group. This breaks the security environment protected by llc_conf_mutex.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

December 30, 2025

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
No patch confirmed yet.
generic

net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe35c24b730d38b421da93ac5d493cb4495e8e54
generic

net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f2f46de98c11d41ac8d22765f47ba54ce5480a5b
generic

net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e40b801b3603a8f90b46acbacdea3505c27f01c0
generic

net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c764cc271d3aa6528ae1b3394babf34ac01f775

Vendor Advisories for CVE-2023-54237(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 6.1.16—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
linux—6.1.20-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.20-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.20-1—

Data Freshness Timeline

(refreshed 12× in last 7d / 35× 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 203 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-14 12:36 UTCEG score recompute
  7. 2026-09-14 12:36 UTCVendor advisory
  8. 2026-09-14 12:36 UTCGHSA enrichment
  9. 2026-09-14 12:02 UTCEG score recompute
  10. 2026-09-14 12:02 UTCVendor advisory
  11. 2026-09-14 12:02 UTCGHSA enrichment
  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-02 14:10 UTCEPSS rescore
  23. 2026-09-01 13:52 UTCEPSS rescore
  24. 2026-09-01 04:36 UTCEPSS rescore
  25. 2026-09-01 01:04 UTCOSV refresh
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-23 00:17 UTCEPSS rescore
  8. 2026-08-23 00:17 UTCEPSS rescore
  9. 2026-08-21 23:47 UTCEPSS rescore
  10. 2026-08-20 22:53 UTCEPSS rescore
  11. 2026-08-19 17:02 UTCEPSS rescore
  12. 2026-08-18 13:46 UTCEPSS rescore
  13. 2026-08-16 14:54 UTCEPSS rescore
  14. 2026-08-16 02:12 UTCEPSS rescore
  15. 2026-08-15 01:28 UTCEPSS rescore
  16. 2026-08-15 01:05 UTCEG score recompute
  17. 2026-08-15 01:05 UTCVendor advisory
  18. 2026-08-15 01:05 UTCGHSA enrichment
  19. 2026-08-13 21:58 UTCEPSS rescore
  20. 2026-08-12 13:49 UTCEPSS rescore
  21. 2026-08-11 13:40 UTCEPSS rescore
  22. 2026-08-10 23:58 UTCEPSS rescore
  23. 2026-08-09 22:22 UTCEG score recompute
  24. 2026-08-09 22:22 UTCVendor advisory
  25. 2026-08-09 22:22 UTCGHSA enrichment
  26. 2026-08-09 13:44 UTCEPSS rescore
  27. 2026-08-08 16:35 UTCEPSS rescore
  28. 2026-08-08 08:55 UTCVendor advisory
  29. 2026-08-08 08:55 UTCGHSA enrichment
  30. 2026-08-08 04:34 UTCEG score recompute
  31. 2026-08-08 04:34 UTCVendor advisory
  32. 2026-08-08 04:34 UTCGHSA enrichment
  33. 2026-08-07 16:25 UTCEPSS rescore
  34. 2026-08-06 13:45 UTCEPSS rescore
  35. 2026-08-06 06:45 UTCEG score recompute
  36. 2026-08-06 06:45 UTCVendor advisory
  37. 2026-08-06 06:45 UTCGHSA enrichment
  38. 2026-08-05 19:15 UTCEPSS rescore
  39. 2026-08-05 19:15 UTCEPSS rescore
  40. 2026-08-05 10:11 UTCEG score recompute
  41. 2026-08-05 10:11 UTCVendor advisory
  42. 2026-08-05 10:11 UTCGHSA enrichment
  43. 2026-08-04 11:27 UTCEG score recompute
  44. 2026-08-04 11:27 UTCVendor advisory
  45. 2026-08-04 11:26 UTCGHSA enrichment
  46. 2026-08-04 10:36 UTCEPSS rescore
  47. 2026-08-04 10:21 UTCEG score recompute▲ 9.80
  48. 2026-08-04 10:21 UTCVendor advisory
  49. 2026-08-04 10:21 UTCGHSA enrichment
  50. 2026-08-04 10:19 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  51. 2026-08-03 10:34 UTCEPSS rescore
  52. 2026-08-02 02:25 UTCEPSS rescore
  53. 2026-08-02 02:25 UTCEPSS rescore
  54. 2026-08-01 04:14 UTCEPSS rescore
  55. 2026-07-30 16:26 UTCEPSS rescore
  56. 2026-07-30 01:29 UTCEPSS rescore
  57. 2026-07-28 15:34 UTCEPSS rescore
  58. 2026-07-28 15:34 UTCEPSS rescore
  59. 2026-07-27 03:09 UTCOSV refresh
  60. 2026-07-26 14:53 UTCEPSS rescore
  61. 2026-07-25 14:16 UTCEPSS rescore
  62. 2026-07-23 14:16 UTCEPSS rescore
  63. 2026-07-23 02:30 UTCEG score recompute
  64. 2026-07-22 23:16 UTCEG score recompute
  65. 2026-07-22 14:07 UTCEPSS rescore
  66. 2026-07-22 14:07 UTCEPSS rescore
  67. 2026-07-21 15:23 UTCEPSS rescore
  68. 2026-07-20 17:06 UTCEPSS rescore
  69. 2026-07-19 14:30 UTCEPSS rescore
  70. 2026-07-19 14:29 UTCEPSS rescore
  71. 2026-07-19 02:27 UTCEPSS rescore
  72. 2026-07-19 02:27 UTCEPSS rescore
  73. 2026-07-18 10:03 UTCEPSS rescore
  74. 2026-07-18 10:03 UTCEPSS rescore
  75. 2026-07-16 17:01 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-54237?
CVE-2023-54237 is a critical vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: net/smc: fix potential panic dues to unprotected smcllcsrvaddlink() There is a certain chance to trigger the following panic: PID: 5900 TASK: ffff88c1c8af4100 CPU: 1 COMMAND: "kworker/1:48" #0 [ffff9456c1cc79a0] machine_kexec at…
When was CVE-2023-54237 disclosed?
CVE-2023-54237 was first published in the National Vulnerability Database on December 30, 2025, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54237 actively exploited?
CVE-2023-54237 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 55.8% of all scored CVEs.
What is the CVSS score of CVE-2023-54237?
CVE-2023-54237 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-54237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54237, 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-54237

Explore →

Is Your Infrastructure Affected by CVE-2023-54237?

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

Start Free Scan →Browse All CVEs