LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53528: RDMA/rxe: Fix unsafe drain work queue code

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix unsafe drain work queue code If create_qp does not fully succeed it is possible for qp cleanup code to attempt to drain the send or recv work queues before the queues have been created causing a seg fault. This patch checks to see if the queues exist before attempting to drain them.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel flaw in the software RDMA/RoCE driver path. If queue-pair creation fails partway through, cleanup can touch queues that were never created, causing a kernel crash. The source bundle does not show active exploitation, CVSS, or a complete product impact statement.

Executive priority

Treat as a targeted availability risk, not a confirmed widespread emergency. Prioritize environments using Linux RDMA/rxe, especially production systems where kernel crashes would interrupt critical workloads.

Technical view

The issue is in RDMA/rxe cleanup logic. After an incomplete create_qp path, send or receive work queue draining may run before those queues exist, leading to a segmentation fault. The cited Linux stable commits add existence checks before draining queues.

Likely exposure

Exposure appears limited to Linux systems using the RDMA/rxe software RDMA stack. The affected-version evidence is incomplete and should be reconciled with distro kernel advisories and the referenced stable commits.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The described impact is a crash during failed queue-pair creation cleanup, not data theft or privilege escalation.

Researcher notes

The public evidence lacks CVSS, CWE, exploit status, and detailed affected-range semantics. The core observable condition is failed queue-pair creation followed by unsafe drain attempts on absent send or receive queues.

Mitigation direction

  • Check Linux vendor advisories for packages containing the referenced stable fixes.
  • Prioritize updates on systems using RDMA/rxe or software RoCE functionality.
  • Avoid inventing local workarounds; follow vendor kernel guidance.
  • Track whether your distribution backported the cited commits.

Validation and detection

  • Inventory hosts with Linux kernels in the potentially affected 6.4 to 6.6 area.
  • Confirm whether RDMA/rxe is present or enabled on those hosts.
  • Map installed kernel packages to vendor advisories or stable commit backports.
  • Review crash telemetry for RDMA/rxe queue-pair creation failures.
Prepared
Confidence
medium
Sources
5

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-53528 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
4Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux49dc9c1f0c7e396654a31a480328fffd902fa494, 49dc9c1f0c7e396654a31a480328fffd902fa494, 49dc9c1f0c7e396654a31a480328fffd902fa494unaffected
LinuxLinux6.4, 0, 6.4.16, 6.5.3, 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.