CVE-2023-53382

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-09-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-29954 (ENISA EUVD) · GHSA-5322-f7jr-cv4m (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/smc: Reset connection when trying to use SMCRv2 fails.

We found a crash when using SMCRv2 with 2 Mellanox ConnectX-4. It can be reproduced by:

  • smc_run nginx
  • smc_run wrk -t 32 -c 500 -d 30 http://:

BUG: kernel NULL pointer dereference, address: 0000000000000014 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 8000000108713067 P4D 8000000108713067 PUD 151127067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 4 PID: 2441 Comm: kworker/4:249 Kdump: loaded Tainted: G W E 6.4.0-rc1+ #42 Workqueue: smc_hs_wq smc_listen_work [smc] RIP: 0010:smc_clc_send_confirm_accept+0x284/0x580 [smc] RSP: 0018:ffffb8294b2d7c78 EFLAGS: 00010a06 RAX: ffff8f1873238880 RBX: ffffb8294b2d7dc8 RCX: 0000000000000000 RDX: 00000000000000b4 RSI: 0000000000000001 RDI: 0000000000b40c00 RBP: ffffb8294b2d7db8 R08: ffff8f1815c5860c R09: 0000000000000000 R10: 0000000000000400 R11: 0000000000000000 R12: ffff8f1846f56180 R13: ffff8f1815c5860c R14: 0000000000000001 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8f1aefd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000014 CR3: 00000001027a0001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? mlx5_ib_map_mr_sg+0xa1/0xd0 [mlx5_ib] ? smcr_buf_map_link+0x24b/0x290 [smc] ? __smc_buf_create+0x4ee/0x9b0 [smc] smc_clc_send_accept+0x4c/0xb0 [smc] smc_listen_work+0x346/0x650 [smc] ? __schedule+0x279/0x820 process_one_work+0x1e5/0x3f0 worker_thread+0x4d/0x2f0 ? __pfx_worker_thread+0x10/0x10 kthread+0xe5/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50

During the CLC handshake, server sequentially tries available SMCRv2 and SMCRv1 devices in smc_listen_work().

If an SMCRv2 device is found. SMCv2 based link group and link will be assigned to the connection. Then assumed that some buffer assignment errors happen later in the CLC handshake, such as RMB registration failure, server will give up SMCRv2 and try SMCRv1 device instead. But the resources assigned to the connection won't be reset.

When server tries SMCRv1 device, the connection creation process will be executed again. Since conn->lnk has been assigned when trying SMCRv2, it will not be set to the correct SMCRv1 link in smcr_lgr_conn_assign_link(). So in such situation, conn->lgr points to correct SMCRv1 link group but conn->lnk points to the SMCRv2 link mistakenly.

Then in smc_clc_send_confirm_accept(), conn->rmb_desc->mr[link->link_idx] will be accessed. Since the link->link_idx is not correct, the related MR may not have been initialized, so crash happens.

| Try SMCRv2 device first | |-> conn->lgr: assign existed SMCRv2 link group; | |-> conn->link: assign existed SMCRv2 link (link_idx may be 1 in SMC_LGR_SYMMETRIC); | |-> sndbuf & RMB creation fails, quit; | | Try SMCRv1 device then | |-> conn->lgr: create SMCRv1 link group and assign; | |-> conn->link: keep SMCRv2 link mistakenly; | |-> sndbuf & RMB creation succeed, only RMB->mr[link_idx = 0] | initialized. | | Then smc_clc_send_confirm_accept() accesses | conn->rmb_desc->mr[conn->link->link_idx, which is 1], then crash. v

This patch tries to fix this by cleaning conn->lnk before assigning link. In addition, it is better to reset the connection and clean the resources assigned if trying SMCRv2 failed in buffer creation or registration.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 18, 2025

Last Modified

August 5, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.1.31 (fixes >=5.16.0)—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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1
  • every version up to 6.1.37-1: fixed in 6.1.37-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 193 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-25 17:28 UTCEG score recompute
  9. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-24 11:35 UTCEG score recompute
  12. 2026-10-24 11:35 UTCGHSA enrichmentGHSA-5322-f7jr-cv4m · GitHub CVSS 5.5
  13. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-19 14:25 UTCOSV refresh
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-10-18 07:41 UTCEG score recompute
  21. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 68 more
  1. 2026-10-12 18:12 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-11 21:38 UTCEG score recompute
  4. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-09-30 16:37 UTCEG score recompute
  15. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-09-26 20:33 UTCOSV refresh
  19. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  26. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-09-07 06:18 UTCOSV refresh
  34. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  39. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  40. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  41. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  42. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  43. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  44. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  45. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  46. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  47. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-20 16:01 UTCOSV refresh
  51. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  52. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  53. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  54. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  55. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  56. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  57. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  58. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  59. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  60. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  61. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  62. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  63. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  64. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  65. 2026-08-05 10:19 UTCEG score recompute
  66. 2026-08-05 10:19 UTCGHSA enrichmentGHSA-5322-f7jr-cv4m · GitHub CVSS 5.5
  67. 2026-08-04 10:58 UTCEG score recompute
  68. 2026-08-04 10:58 UTCGHSA enrichmentGHSA-5322-f7jr-cv4m · GitHub CVSS 5.5

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-53382?
CVE-2023-53382 is a medium-severity vulnerability; its CVE record was published on September 18, 2025. In the Linux kernel, the following vulnerability has been resolved: net/smc: Reset connection when trying to use SMCRv2 fails. We found a crash when using SMCRv2 with 2 Mellanox ConnectX-4. It can be reproduced by: smc_run nginx smc_run wrk -t 32 -c 500 -d 30 http://<ip>:<port> BUG: kernel NULL…
When was the CVE record for CVE-2023-53382 published?
The CVE record for CVE-2023-53382 was published on September 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53382 actively exploited?
CVE-2023-53382 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53382?
CVE-2023-53382 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53382?
A fix for CVE-2023-53382 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53382

Explore →

Is Your Infrastructure Affected by CVE-2023-53382?

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

Book a Demo →Browse All CVEs