LiveActive security incident?Get immediate response
CVE Record

CVE-2024-47695: RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path->s.con_num. This commits resets the cid to clt_path->s.con_num - 1, to stay in bounds in the cleanup loop later.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux RDMA RTRS client cleanup error can access memory beyond an allocated connection array when connection setup fails. This may crash or corrupt affected systems. The supplied CVSS rating is 9.8, but the sources do not establish practical attacker control or real-world exploitation.

Executive priority

Treat as urgent on infrastructure using RDMA RTRS, especially where service disruption or kernel compromise would have high impact. Prioritize exposure confirmation and supported kernel updates. Systems without this functionality are less likely to be exposed, but that should be verified rather than assumed.

Technical view

In init_conns(), a failed create_con() or create_cm() path leaves cid equal to con_num. The subsequent cleanup loop uses that out-of-range index after destroying a tag. The Linux fix resets cid to con_num minus one before cleanup.

Likely exposure

Exposure is limited to Linux systems running an affected kernel and using the RDMA RTRS client functionality. The bundle lists multiple affected kernel lines, but its flattened version data is ambiguous; confirm exact vulnerable and corrected package versions through kernel or distribution advisories.

Exploitation context

The CVSS vector characterizes this as network-accessible, low-complexity, unauthenticated, and requiring no user interaction. However, KEV is false, and the supplied sources provide no evidence of active exploitation, a public exploit, or reliable attacker control over the initialization failure.

Researcher notes

The documented defect is an out-of-bounds cleanup access reached after connection-creation failure. The sources do not identify the accessed object, memory-safety outcome, attacker-controlled inputs, or demonstrated confidentiality and integrity impact. The 9.8 score should therefore be considered alongside deployment-specific reachability and trigger analysis.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable cited fix or backport.
  • Check Linux distribution advisories for corrected package versions before deployment.
  • Prioritize systems actively using RDMA RTRS client functionality.
  • Consult vendor guidance for temporary mitigations if immediate kernel updating is impossible.

Validation and detection

  • Inventory kernel versions and identify systems loading or using the RDMA RTRS client.
  • Compare installed kernel changelogs against the applicable cited fix commit.
  • Confirm corrected kernel package versions with the operating-system vendor.
  • After updating, verify the new kernel is running and RDMA workloads operate normally.
Prepared
Confidence
medium
Sources
9

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-47695 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
8Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-47695Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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

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

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6a98d71daea186247005099758af549e6afdd244, 6a98d71daea186247005099758af549e6afdd244, 6a98d71daea186247005099758af549e6afdd244, 6a98d71daea186247005099758af549e6afdd244, 6a98d71daea186247005099758af549e6afdd244, 6a98d71daea186247005099758af549e6afdd244unaffected
LinuxLinux5.8, 0, 5.15.168, 6.1.113, 6.6.54, 6.10.13, 6.11.2, 6.12affected
Weakness

CWE details

No CWE listed

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