CVE-2023-54318

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-30. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add

While doing smcr_port_add, there maybe linkgroup add into or delete from smc_lgr_list.list at the same time, which may result kernel crash. So, use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add.

The crash calltrace show below: BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 0 PID: 559726 Comm: kworker/0:92 Kdump: loaded Tainted: G Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 449e491 04/01/2014 Workqueue: events smc_ib_port_event_work [smc] RIP: 0010:smcr_port_add+0xa6/0xf0 [smc] RSP: 0000:ffffa5a2c8f67de0 EFLAGS: 00010297 RAX: 0000000000000001 RBX: ffff9935e0650000 RCX: 0000000000000000 RDX: 0000000000000010 RSI: ffff9935e0654290 RDI: ffff9935c8560000 RBP: 0000000000000000 R08: 0000000000000000 R09: ffff9934c0401918 R10: 0000000000000000 R11: ffffffffb4a5c278 R12: ffff99364029aae4 R13: ffff99364029aa00 R14: 00000000ffffffed R15: ffff99364029ab08 FS: 0000000000000000(0000) GS:ffff994380600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000f06a10003 CR4: 0000000002770ef0 PKRU: 55555554 Call Trace: smc_ib_port_event_work+0x18f/0x380 [smc] process_one_work+0x19b/0x340 worker_thread+0x30/0x370 ? process_one_work+0x340/0x340 kthread+0x114/0x130 ? __kthread_cancel_work+0x50/0x50 ret_from_fork+0x1f/0x30

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

Published

December 30, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70c8d17007dc4a07156b7da44509527990e569b3
generic

net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06b4934ab2b534bb92935c7601852066ebb9eab8
generic

net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d1c6c93c27a4bf48006ab16cd9b38d85559d7645

Vendor Advisories for CVE-2023-54318(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 @ 5.10.195—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 ... 5.10.92-2 (34 versions)5.10.197-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (10 versions)6.1.55-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.6-1—

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

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2023-54318?
CVE-2023-54318 is a high vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: net/smc: use smclgrlist.lock to protect smclgrlist.list iterate in smcrportadd While doing smcrportadd, there maybe linkgroup add into or delete from smclgrlist.list at the same time, which may result kernel crash. So, use…
When was CVE-2023-54318 disclosed?
CVE-2023-54318 was first published in the National Vulnerability Database on December 30, 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-54318 actively exploited?
CVE-2023-54318 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 80.8% of all scored CVEs.
What is the CVSS score of CVE-2023-54318?
CVE-2023-54318 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54318, 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-54318

Explore →

Is Your Infrastructure Affected by CVE-2023-54318?

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

Start Free Scan →Browse All CVEs