LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54318: net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-54318 is a Linux kernel reliability flaw in the SMC networking code. A race while adding an SMC-R port can leave the kernel reading an invalid list entry, causing a kernel crash. The provided sources do not show data theft, privilege escalation, CVSS, or active exploitation.

Executive priority

Patch through normal kernel maintenance, with faster handling for high-availability Linux systems that use SMC/RDMA networking. Business risk is service interruption from kernel crash, not confirmed compromise based on current sources.

Technical view

The fix adds smc_lgr_list.lock protection while smcr_port_add iterates smc_lgr_list.list. Concurrent link-group add or delete operations could otherwise trigger a NULL pointer dereference in smcr_port_add, observed from smc_ib_port_event_work in the crash trace. Upstream stable commits are referenced as the remediation source.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel builds with SMC/SMC-R code in use or reachable through relevant networking and RDMA-related events. The bundle does not identify affected distributions, kernel configurations, cloud images, or package names.

Exploitation context

The source bundle describes a concurrency crash and marks KEV as false. It provides no public exploit claim, exploitation-in-the-wild evidence, or weaponized technique. Treat this primarily as a kernel denial-of-service risk unless vendor advisories add more impact.

Researcher notes

Evidence supports a missing-lock race in Linux net/smc. The affected-version data in the bundle is incomplete and flattened, so avoid over-precise range claims without the full CVE JSON or distribution advisories. No CWE, CVSS, or exploit status is provided.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for exact fixed package versions.
  • Prioritize systems using SMC, SMC-R, RDMA, or related kernel modules.
  • Where patching is delayed, review vendor guidance for disabling unused SMC functionality.
  • Monitor kernel crash logs for smcr_port_add or smc_ib_port_event_work traces.

Validation and detection

  • Inventory Linux kernel versions across affected server fleets.
  • Confirm whether SMC or SMC-R kernel modules are present or loaded.
  • Map installed kernels against vendor advisories and referenced stable commits.
  • Review dmesg, kdump, and crash reports for matching NULL dereference traces.
  • Verify patched kernels are booted, not merely installed.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54318 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1f90a05d9ff907c70456e7c9d7058372679a88c6, 1f90a05d9ff907c70456e7c9d7058372679a88c6, 1f90a05d9ff907c70456e7c9d7058372679a88c6, 1f90a05d9ff907c70456e7c9d7058372679a88c6, 1f90a05d9ff907c70456e7c9d7058372679a88c6unaffected
LinuxLinux5.8, 0, 5.10.195, 5.15.132, 6.1.54, 6.5.4, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.