LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42285: RDMA/iwcm: Fix a use-after-free related to destroying CM IDs

In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix a use-after-free related to destroying CM IDs iw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with an existing struct iw_cm_id (cm_id) as follows: conn_id->cm_id.iw = cm_id; cm_id->context = conn_id; cm_id->cm_handler = cma_iw_handler; rdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make sure that cm_work_handler() does not trigger a use-after-free by only freeing of the struct rdma_id_private after all pending work has finished.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux kernel timing flaw can let RDMA connection-management work access memory after it has been freed. The supplied CVSS rating is 9.8, indicating potentially severe confidentiality, integrity, and availability impact. Actual risk depends on whether affected kernel code and RDMA IWCM functionality are present and reachable.

Executive priority

Treat remediation as urgent for affected systems using RDMA, especially those exposed to untrusted networks. Prioritize inventory and vendor package confirmation because the severity is critical, while recognizing that the supplied evidence does not establish active exploitation or universal exposure across Linux hosts.

Technical view

The flaw occurs when rdma_destroy_id() frees an iw_cm_id and its associated rdma_id_private while cm_work_handler() can still process pending work referencing that memory. The stable fix defers freeing rdma_id_private until pending work completes, preventing the use-after-free condition.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds where the RDMA IWCM path is available or used. The supplied version data includes multiple upstream and stable versions, but downstream distribution backports may differ. Exact exposure requires package-level verification with the relevant Linux distributor.

Exploitation context

The bundle reports no CISA KEV listing and provides no cited evidence of active exploitation or a public exploit. The supplied CVSS vector describes a network-reachable, low-complexity attack requiring neither privileges nor user interaction, but demonstrated exploitability and environmental prerequisites are not documented here.

Researcher notes

This is a lifetime-synchronization defect involving conn_id, cm_id, rdma_destroy_id(), and asynchronous cm_work_handler() processing. Review the stable-branch commits for exact backport context. The bundle supplies no CWE, proof of concept, crash signature, exploitation telemetry, or detailed trigger prerequisites, limiting exploitability assessment.

Mitigation direction

  • Apply the Linux or distribution kernel update containing the applicable stable fix.
  • Follow distributor guidance to identify the corrected downstream kernel package.
  • Reboot affected systems into the updated kernel after installation.
  • If patching is delayed, seek vendor-supported guidance for limiting RDMA IWCM exposure.

Validation and detection

  • Inventory running kernel versions and distribution package builds across Linux systems.
  • Identify systems with RDMA IWCM functionality available or actively used.
  • Confirm each running kernel contains the relevant upstream fix or distributor backport.
  • Verify systems booted into the updated kernel rather than merely installing it.
  • Monitor vendor advisories for corrected package versions and revised exposure information.
Prepared
Confidence
medium
Sources
6

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-42285 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
11Source 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-42285Attack 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
LinuxLinux59c68ac31e15ad09d2cb04734e3c8c544a95f8d4, 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4, 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4, 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4, 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4, 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4, 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4, 59c68ac31e15ad09d2cb04734e3c8c544a95f8d4unaffected
LinuxLinux4.8, 0, 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103, 6.6.44, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

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