CWE
476
EPSS
0.044%
Advisory Published
CVE Published
Updated

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

First published: Sun May 19 2024(Updated: )

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

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=4.19.310<4.19.312
Linux Kernel>=5.4.272<5.7.274
Linux Kernel>=5.10.213<5.10.215
Linux Kernel>=5.15.152<5.15.154
Linux Kernel>=6.1.82<6.1.85
Linux Kernel>=6.6.22<6.6.26
Linux Kernel>=6.7.10<6.8.5
Linux Kernel=6.9-rc1
Linux Kernel=6.9-rc2
Debian Linux=10.0
debian/linux
5.10.223-1
5.10.234-1
6.1.129-1
6.1.128-1
6.12.20-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-35902?

    CVE-2024-35902 is considered a medium severity vulnerability due to its potential to cause null dereference issues in the Linux kernel.

  • How do I fix CVE-2024-35902?

    To fix CVE-2024-35902, upgrade to the patched versions of the Linux kernel specified in the vulnerability report.

  • Which versions of the Linux kernel are affected by CVE-2024-35902?

    CVE-2024-35902 affects specific versions of the Linux kernel between 4.19.310 and 4.19.312, as well as several ranges from 5.4.272 to 6.9-rc2.

  • What causes the null dereference in CVE-2024-35902?

    The null dereference in CVE-2024-35902 is caused by the parameter 'cp' being potentially null when attempting to access 'cp->cp_conn'.

  • Is there a workaround for CVE-2024-35902?

    There is no documented workaround for CVE-2024-35902, and updating to a secure kernel version is the recommended action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203