high
7
CWE
416 362
Advisory Published
Updated

CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync

First published: Fri Sep 27 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: Fix uaf in __timer_delete_sync There are two paths to access mptcp_pm_del_add_timer, result in a race condition: CPU1 CPU2 ==== ==== net_rx_action napi_poll netlink_sendmsg __napi_poll netlink_unicast process_backlog netlink_unicast_kernel __netif_receive_skb genl_rcv __netif_receive_skb_one_core netlink_rcv_skb NF_HOOK genl_rcv_msg ip_local_deliver_finish genl_family_rcv_msg ip_protocol_deliver_rcu genl_family_rcv_msg_doit tcp_v4_rcv mptcp_pm_nl_flush_addrs_doit tcp_v4_do_rcv mptcp_nl_remove_addrs_list tcp_rcv_established mptcp_pm_remove_addrs_and_subflows tcp_data_queue remove_anno_list_by_saddr mptcp_incoming_options mptcp_pm_del_add_timer mptcp_pm_del_add_timer kfree(entry) In remove_anno_list_by_saddr(running on CPU2), after leaving the critical zone protected by "pm.lock", the entry will be released, which leads to the occurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1). Keeping a reference to add_timer inside the lock, and calling sk_stop_timer_sync() with this reference, instead of "entry->add_timer". Move list_del(&entry->list) to mptcp_pm_del_add_timer and inside the pm lock, do not directly access any members of the entry outside the pm lock, which can avoid similar "entry->x" uaf.

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

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.10<6.1.111
Linux Kernel>=6.2<6.6.52
Linux Kernel>=6.7<6.10.11
Linux Kernel=6.11-rc1
Linux Kernel=6.11-rc2
Linux Kernel=6.11-rc3
Linux Kernel=6.11-rc4
Linux Kernel=6.11-rc5
Linux Kernel=6.11-rc6
Linux Kernel=6.11-rc7
debian/linux<=5.10.223-1<=5.10.226-1
6.1.123-1
6.1.119-1
6.12.11-1
debian/linux-6.1
6.1.119-1~deb11u1

Remedy

https://git.kernel.org/stable/c/12134a652b0a10064844ea235173e70246eba6dc

Remedy

https://git.kernel.org/stable/c/6452b162549c7f9ef54655d3fb9977b9192e6e5b

Remedy

https://git.kernel.org/stable/c/67409b358500c71632116356a0b065f112d7b707

Remedy

https://git.kernel.org/stable/c/b4cd80b0338945a94972ac3ed54f8338d2da2076

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

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

    CVE-2024-46858 has a medium severity rating due to its potential for causing a use-after-free condition leading to denial of service.

  • How do I fix CVE-2024-46858?

    To remediate CVE-2024-46858, upgrade to a patched version of the Linux Kernel such as 6.1.123-1 or later.

  • Which versions of the Linux Kernel are affected by CVE-2024-46858?

    CVE-2024-46858 affects Linux Kernel versions from 5.10 to 6.11-rc7, excluding certain patched releases.

  • What components are involved in CVE-2024-46858?

    CVE-2024-46858 involves the multipath TCP (MPTCP) implementation in the Linux Kernel.

  • Is CVE-2024-46858 a local or remote vulnerability?

    CVE-2024-46858 is primarily a local vulnerability that may be exploited in specific environments under certain conditions.

Company

Resources

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