LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40992: RDMA/rxe: Fix responder length checking for UD request packets

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix responder length checking for UD request packets According to the IBA specification: If a UD request packet is detected with an invalid length, the request shall be an invalid request and it shall be silently dropped by the responder. The responder then waits for a new request packet. commit 689c5421bfe0 ("RDMA/rxe: Fix incorrect responder length checking") defers responder length check for UD QPs in function `copy_data`. But it introduces a regression issue for UD QPs. When the packet size is too large to fit in the receive buffer. `copy_data` will return error code -EINVAL. Then `send_data_in` will return RESPST_ERR_MALFORMED_WQE. UD QP will transfer into ERROR state.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A remotely supplied, oversized RDMA/rxe unreliable-datagram request can incorrectly force the receiving queue pair into an error state instead of being silently discarded. This can interrupt affected RDMA communications, creating an availability risk. The supplied CVSS score is 7.5, with no indicated confidentiality or integrity impact.

Executive priority

Treat as a high-priority availability issue where RDMA/rxe supports critical or network-accessible workloads. Establish exposure quickly, then apply vendor-supported fixed kernels during an expedited maintenance window. Lower the priority for systems where RDMA/rxe UD functionality is absent or inaccessible.

Technical view

Linux RDMA/rxe responder length validation regressed after commit 689c5421bfe0. When a UD packet exceeds the receive buffer, copy_data returns -EINVAL, send_data_in reports RESPST_ERR_MALFORMED_WQE, and the UD queue pair enters ERROR state. Correct behavior is to discard the invalid request and continue waiting.

Likely exposure

Exposure is limited to Linux systems using the RDMA/rxe subsystem with unreliable-datagram queue pairs. The bundle identifies affected versions including 6.2, 6.6.36, 6.9.7, and 6.10, but distribution backports may change actual status. Systems not using this functionality are unlikely to be practically exposed.

Exploitation context

The CVSS vector describes network-reachable, low-complexity, unauthenticated availability impact without user interaction. However, the bundle reports no CISA KEV listing and provides no evidence of active exploitation or a public exploit. Practical reachability depends on whether RDMA/rxe UD traffic is enabled and accessible.

Researcher notes

The flaw is a regression in responder handling, not a stated memory-corruption issue. Its documented consequence is transition of a UD queue pair into ERROR state after an oversized request cannot fit the receive buffer. The source bundle names three stable fix commits but does not map each commit to a specific release branch.

Mitigation direction

  • Identify systems using Linux RDMA/rxe and unreliable-datagram queue pairs.
  • Prioritize exposed or business-critical RDMA services for remediation.
  • Obtain a distribution kernel containing the applicable upstream stable fix.
  • Consult vendor guidance to account for kernel backports and release-specific versioning.
  • Restrict unnecessary network access to affected RDMA services while remediation is pending.

Validation and detection

  • Record running kernel versions on systems providing RDMA/rxe services.
  • Confirm whether RDMA/rxe and unreliable-datagram queue pairs are actively used.
  • Map distribution kernel builds against the three referenced stable fixes.
  • Verify updated kernels include the applicable fix or documented vendor backport.
  • Confirm UD queue pairs remain operational during approved resilience testing.
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-2024-40992 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-40992Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux689c5421bfe0eac65526bd97a466b9590a6aad3c, 689c5421bfe0eac65526bd97a466b9590a6aad3c, 689c5421bfe0eac65526bd97a466b9590a6aad3cunaffected
LinuxLinux6.2, 0, 6.6.36, 6.9.7, 6.10affected
Weakness

CWE details

No CWE listed

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