LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53539: RDMA/rxe: Fix incomplete state save in rxe_requester

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix incomplete state save in rxe_requester If a send packet is dropped by the IP layer in rxe_requester() the call to rxe_xmit_packet() can fail with err == -EAGAIN. To recover, the state of the wqe is restored to the state before the packet was sent so it can be resent. However, the routines that save and restore the state miss a significnt part of the variable state in the wqe, the dma struct which is used to process through the sge table. And, the state is not saved before the packet is built which modifies the dma struct. Under heavy stress testing with many QPs on a fast node sending large messages to a slow node dropped packets are observed and the resent packets are corrupted because the dma struct was not restored. This patch fixes this behavior and allows the test cases to succeed.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can corrupt resent RDMA RXE packets after packet drops under heavy stress. The public record describes reliability and data-integrity impact, not remote code execution. Business urgency is highest for systems using Linux software RDMA/RXE with large RDMA messages or high queue-pair counts.

Executive priority

Treat as a targeted operational integrity issue. Patch affected RDMA/RXE systems during the next appropriate maintenance window, sooner where RDMA data correctness is business-critical.

Technical view

The RDMA rxe_requester retry path restores work queue element state after rxe_xmit_packet() returns -EAGAIN, but did not preserve the DMA state used to walk SGEs. Because packet building changed that state, retransmission could use corrupted state and send corrupted packets. Stable kernel fixes are referenced.

Likely exposure

Exposure appears limited to Linux systems using the RDMA RXE software driver. General Linux hosts without RXE/RDMA workloads are less likely to be affected. Exact fixed distribution package versions are not provided in the bundle.

Exploitation context

No active exploitation is cited, and KEV is false. The described trigger is heavy stress testing with many QPs, fast-to-slow node traffic, large messages, dropped packets, and retry behavior.

Researcher notes

Evidence is kernel-focused and sparse: no CVSS, CWE, CPE, or exploit advisory is included. The affected-version data appears commit and stable-branch oriented, so validate exposure through kernel source/package backports.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize Linux hosts running RXE or software RDMA workloads.
  • Check distribution advisories for exact fixed package versions.
  • If patching is delayed, ask the vendor for supported RXE risk-reduction guidance.

Validation and detection

  • Inventory hosts with Linux RDMA RXE enabled or in use.
  • Compare running kernels against vendor advisories and referenced stable commits.
  • Review RDMA workload testing for packet corruption or retry-related failures.
  • Confirm updated kernels include the RXE state-save fix.
Prepared
Confidence
medium
Sources
6

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-53539 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
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3050b99850247695cb07a5c15265afcc08bcf400, 3050b99850247695cb07a5c15265afcc08bcf400, 3050b99850247695cb07a5c15265afcc08bcf400, 3050b99850247695cb07a5c15265afcc08bcf400unaffected
LinuxLinux4.8, 0, 6.1.53, 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.