UBUNTU-CVE-2024-35902
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
02 / AFFECTED SOFTWARE
Affected packages
29 explicit affected versions
40 explicit affected versions
1 explicit affected versions
31 explicit affected versions
37 explicit affected versions
8 explicit affected versions
40 explicit affected versions
7 explicit affected versions
51 explicit affected versions
26 explicit affected versions
45 explicit affected versions
37 explicit affected versions
10 explicit affected versions
10 explicit affected versions
13 explicit affected versions
13 explicit affected versions
38 explicit affected versions
1 explicit affected versions
37 explicit affected versions
6 explicit affected versions
8 explicit affected versions
4 explicit affected versions
8 explicit affected versions
47 explicit affected versions
27 explicit affected versions
23 explicit affected versions
7 explicit affected versions
10 explicit affected versions
8 explicit affected versions
54 explicit affected versions
3 explicit affected versions
33 explicit affected versions
16 explicit affected versions
4 explicit affected versions
12 explicit affected versions
38 explicit affected versions
51 explicit affected versions
13 explicit affected versions
34 explicit affected versions
32 explicit affected versions
10 explicit affected versions
40 explicit affected versions
10 explicit affected versions
13 explicit affected versions
9 explicit affected versions
10 explicit affected versions
7 explicit affected versions
8 explicit affected versions
8 explicit affected versions
21 explicit affected versions
6 explicit affected versions
13 explicit affected versions
12 explicit affected versions
7 explicit affected versions
7 explicit affected versions
12 explicit affected versions
11 explicit affected versions
5 explicit affected versions
26 explicit affected versions
2 explicit affected versions
1 explicit affected versions
2 explicit affected versions
40 explicit affected versions
8 explicit affected versions
23 explicit affected versions
37 explicit affected versions
5 explicit affected versions
39 explicit affected versions
3 explicit affected versions
48 explicit affected versions
26 explicit affected versions
12 explicit affected versions
46 explicit affected versions
12 explicit affected versions
44 explicit affected versions
2 explicit affected versions
40 explicit affected versions
51 explicit affected versions
4 explicit affected versions
4 explicit affected versions
16 explicit affected versions
6 explicit affected versions
9 explicit affected versions
12 explicit affected versions
13 explicit affected versions
5 explicit affected versions
7 explicit affected versions
21 explicit affected versions
7 explicit affected versions
10 explicit affected versions
14 explicit affected versions
6 explicit affected versions
18 explicit affected versions
3 explicit affected versions
16 explicit affected versions
43 explicit affected versions
51 explicit affected versions
49 explicit affected versions
9 explicit affected versions
43 explicit affected versions
2 explicit affected versions
11 explicit affected versions
23 explicit affected versions
35 explicit affected versions
12 explicit affected versions
7 explicit affected versions
6 explicit affected versions
12 explicit affected versions
50 explicit affected versions
12 explicit affected versions
48 explicit affected versions
27 explicit affected versions
35 explicit affected versions
12 explicit affected versions
7 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
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
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/62fc3357e079a07a22465b9b6ef71bb6ea75ee4b
- https://git.kernel.org/stable/c/62fc3357e079a07a22465b9b6ef71bb6ea75ee4b
- https://git.kernel.org/stable/c/6794090c742008c53b344b35b021d4a3093dc50a
- https://git.kernel.org/stable/c/92309bed3c5fbe2ccd4c45056efd42edbd06162d
- https://git.kernel.org/stable/c/bcd46782e2ec3825d10c1552fcb674d491cc09f9
- https://git.kernel.org/stable/c/cbaac2e5488ed54833897264a5ffb2a341a9f196
- https://git.kernel.org/stable/c/cfb786b03b03c5ff38882bee38525eb9987e4d14
- https://git.kernel.org/stable/c/d275de8ea7be3a453629fddae41d4156762e814c
- https://git.kernel.org/stable/c/d49fac38479bfdaec52b3ea274d290c47a294029
- https://ubuntu.com/security/CVE-2024-35902
- https://ubuntu.com/security/notices/USN-6893-1
- https://ubuntu.com/security/notices/USN-6893-2
- https://ubuntu.com/security/notices/USN-6893-3
- https://ubuntu.com/security/notices/USN-6898-1
- https://ubuntu.com/security/notices/USN-6898-2
- https://ubuntu.com/security/notices/USN-6898-3
- https://ubuntu.com/security/notices/USN-6898-4
- https://ubuntu.com/security/notices/USN-6917-1
- https://ubuntu.com/security/notices/USN-6918-1
- https://ubuntu.com/security/notices/USN-6927-1
- https://ubuntu.com/security/notices/USN-7019-1
- https://www.cve.org/CVERecord?id=CVE-2024-35902