net/rds: fix possible cp null dereference

Description

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

Timeline

Scores

EPSS (exploitation in 30 days)

0.22% · top 87% of all CVEs (11 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

• Linux · Linux

  • affected 786854141057751bc08eb26f1b02e97c1631c8f4 – < d275de8ea7be3a453629fddae41d4156762e814c
  • affected 997efea2bf3a4adb96c306b9ad6a91442237bf5b – < bcd46782e2ec3825d10c1552fcb674d491cc09f9
  • affected 9dfc15a10dfd44f8ff7f27488651cb5be6af83c2 – < cfb786b03b03c5ff38882bee38525eb9987e4d14
  • affected b562ebe21ed9adcf42242797dd6cb75beef12bf0 – < d49fac38479bfdaec52b3ea274d290c47a294029
  • affected 998fd719e6d6468b930ac0c44552ea9ff8b07b80 – < cbaac2e5488ed54833897264a5ffb2a341a9f196
  • affected 2b505d05280739ce31d5708da840f42df827cb85 – < 92309bed3c5fbe2ccd4c45056efd42edbd06162d
  • affected c055fc00c07be1f0df7375ab0036cebd1106ed38 – < 6794090c742008c53b344b35b021d4a3093dc50a
  • affected c055fc00c07be1f0df7375ab0036cebd1106ed38 – < 62fc3357e079a07a22465b9b6ef71bb6ea75ee4b
  • affected 907761307469adecb02461a14120e9a1812a5fb1
  • affected 4.19.310 – < 4.19.312
  • affected 5.4.272 – < 5.4.274
  • affected 5.10.213 – < 5.10.215
  • affected 5.15.152 – < 5.15.154
  • affected 6.1.82 – < 6.1.85
  • affected 6.6.22 – < 6.6.26
  • affected 6.7.10 – < 6.8

• Linux · Linux

  • affected 6.8
  • unaffected < 6.8
  • unaffected 4.19.312 – ≤ 4.19.*
  • unaffected 5.4.274 – ≤ 5.4.*
  • unaffected 5.10.215 – ≤ 5.10.*
  • unaffected 5.15.154 – ≤ 5.15.*
  • unaffected 6.1.85 – ≤ 6.1.*
  • unaffected 6.6.26 – ≤ 6.6.*
  • unaffected 6.8.5 – ≤ 6.8.*
  • unaffected 6.9 – ≤ *

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2024-35620 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2024-35902](https://cveledger.app/badge/CVE-2024-35902.svg)](https://cveledger.app/cve/CVE-2024-35902)

Record last updated 15 Oct 2026, 00:41 UTC.