net/rds: fix possible cp null dereference
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.85, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 786854141057751bc08eb26f1b02e97c1631c8f4 · fixed in d275de8ea7be3a453629fddae41d4156762e814c; From 997efea2bf3a4adb96c306b9ad6a91442237bf5b · fixed in bcd46782e2ec3825d10c1552fcb674d491cc09f9; From 9dfc15a10dfd44f8ff7f27488651cb5be6af83c2 · fixed in cfb786b03b03c5ff38882bee38525eb9987e4d14; From b562ebe21ed9adcf42242797dd6cb75beef12bf0 · fixed in d49fac38479bfdaec52b3ea274d290c47a294029; From 998fd719e6d6468b930ac0c44552ea9ff8b07b80 · fixed in cbaac2e5488ed54833897264a5ffb2a341a9f196; From 2b505d05280739ce31d5708da840f42df827cb85 · fixed in 92309bed3c5fbe2ccd4c45056efd42edbd06162d; From c055fc00c07be1f0df7375ab0036cebd1106ed38 · fixed in 6794090c742008c53b344b35b021d4a3093dc50a; From c055fc00c07be1f0df7375ab0036cebd1106ed38 · fixed in 62fc3357e079a07a22465b9b6ef71bb6ea75ee4b; From 4.19.310 · fixed in 4.19.312; From 5.4.272 · fixed in 5.4.274; From 5.10.213 · fixed in 5.10.215; From 5.15.152 · fixed in 5.15.154; From 6.1.82 · fixed in 6.1.85; From 6.6.22 · fixed in 6.6.26; From 6.7.10 · fixed in 6.8
- Linux Linux
6.8
- KernelLinux
fixed in 4.19.312; From 4.20.0 · fixed in 5.4.274; From 5.5.0 · fixed in 5.10.215; From 5.11.0 · fixed in 5.15.154; From 5.16.0 · fixed in 6.1.85; From 6.2.0 · fixed in 6.6.26; From 6.7.0 · fixed in 6.8.5
References 8
git.kernel.org
- stable/c/d275de8ea7be3a453629fddae41d4156762e814c
- stable/c/bcd46782e2ec3825d10c1552fcb674d491cc09f9
- stable/c/cfb786b03b03c5ff38882bee38525eb9987e4d14
- stable/c/d49fac38479bfdaec52b3ea274d290c47a294029
- stable/c/cbaac2e5488ed54833897264a5ffb2a341a9f196
- stable/c/92309bed3c5fbe2ccd4c45056efd42edbd06162d
- stable/c/6794090c742008c53b344b35b021d4a3093dc50a
- stable/c/62fc3357e079a07a22465b9b6ef71bb6ea75ee4b