LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35902: net/rds: fix possible cp null dereference

In the Linux kernel, the following vulnerability has been resolved: net/rds: fix possible cp null dereference cp might be null, calling cp->cp_conn would produce null dereference [Simon Horman adds:] Analysis: * cp is a parameter of __rds_rdma_map and is not reassigned. * The following call-sites pass a NULL cp argument to __rds_rdma_map() - rds_get_mr() - rds_get_mr_for_dest * Prior to the code above, the following assumes that cp may be NULL (which is indicative, but could itself be unnecessary) trans_private = rs->rs_transport->get_mr( sg, nents, rs, &mr->r_key, cp ? cp->cp_conn : NULL, args->vec.addr, args->vec.bytes, need_odp ? ODP_ZEROBASED : ODP_NOT_NEEDED); * The code modified by this patch is guarded by IS_ERR(trans_private), where trans_private is assigned as per the previous point in this analysis. The only implementation of get_mr that I could locate is rds_ib_get_mr() which can return an ERR_PTR if the conn (4th) argument is NULL. * ret is set to PTR_ERR(trans_private). rds_ib_get_mr can return ERR_PTR(-ENODEV) if the conn (4th) argument is NULL. Thus ret may be -ENODEV in which case the code in question will execute. Conclusion: * cp may be NULL at the point where this patch adds a check; this patch does seem to address a possible bug

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue fixes a possible crash in the RDS networking code when a connection pointer is unexpectedly null. The public record does not provide CVSS, CWE, or confirmed impact details. Treat it as an availability-oriented kernel maintenance risk, especially on systems using RDS or RDMA-related functionality.

Executive priority

Handle through normal kernel patch governance, with higher priority for Linux infrastructure using RDS/RDMA or covered by Debian or Siemens advisories. There is no provided evidence of active exploitation, but kernel crash risks can still affect availability-sensitive systems.

Technical view

The flaw is in net/rds within __rds_rdma_map(). Some call sites can pass a null cp argument, and later error handling could dereference cp->cp_conn. The kernel stable commits add a null check around that path. The record links fixes across supported stable branches.

Likely exposure

Exposure is most relevant to Linux systems with affected kernel builds and RDS/RDMA code paths available. The source bundle lists Linux kernel affected version data and stable commits, but does not prove which distributions or appliances are vulnerable beyond linked Debian and Siemens references.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. It describes a possible null pointer dereference, not a public exploit. Without additional vendor analysis, practical reachability and required privileges are not established in the provided sources.

Researcher notes

Key evidence is the kernel analysis showing cp can be null at __rds_rdma_map() and may be dereferenced during error handling. The record lacks CVSS, CWE, exploitability details, and privilege requirements, so conclusions should remain limited to the documented null dereference fix.

Mitigation direction

  • Apply kernel updates from the relevant Linux distribution or vendor advisory.
  • Review Debian LTS and Siemens advisories if those environments apply.
  • Prioritize systems using RDS, RDMA, or InfiniBand-related workloads.
  • If patching is delayed, check vendor guidance for supported temporary controls.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Compare installed kernels with vendor advisories and stable fix references.
  • Identify whether RDS/RDMA-related modules or workloads are present.
  • Confirm patched kernels are running after maintenance reboots.
Prepared
Confidence
medium
Sources
12

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-35902 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
3ADP providers
12Source 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
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux786854141057751bc08eb26f1b02e97c1631c8f4, 997efea2bf3a4adb96c306b9ad6a91442237bf5b, 9dfc15a10dfd44f8ff7f27488651cb5be6af83c2, b562ebe21ed9adcf42242797dd6cb75beef12bf0, 998fd719e6d6468b930ac0c44552ea9ff8b07b80, 2b505d05280739ce31d5708da840f42df827cb85, c055fc00c07be1f0df7375ab0036cebd1106ed38, c055fc00c07be1f0df7375ab0036cebd1106ed38, 907761307469adecb02461a14120e9a1812a5fb1unaffected
LinuxLinux6.8, 0, 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.85, 6.6.26, 6.8.5, 6.9affected
Weakness

CWE details

No CWE listed

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