CVE-2024-46858 remediation guide

Linux Linux, linux kernel

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_e...

Open CVE record

ProductLinux Linux, linux kernel

Affected versions>= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 0e7814b028cd50b3ff79659d23dfa9da6a1e75e1, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 3554482f4691571fc4b5490c17ae26896e62171c, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 67409b358500c71632116356a0b065f112d7b707, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 6452b162549c7f9ef54655d3fb9977b9192e6e5b, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 12134a652b0a10064844ea235173e70246eba6dc, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < b4cd80b0338945a94972ac3ed54f8338d2da2076, >= 5.10, >= 5.10 < 6.1.111, >= 6.2 < 6.6.52, >= 6.7 < 6.10.11, 6.11

Fixed versions6.1.111, 6.6.52, 6.10.11

Priority basisReview · CVSS 7 · EPSS -

Identify the affected asset

Confirm whether Linux Linux, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 0e7814b028cd50b3ff79659d23dfa9da6a1e75e1, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 3554482f4691571fc4b5490c17ae26896e62171c, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 67409b358500c71632116356a0b065f112d7b707, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 6452b162549c7f9ef54655d3fb9977b9192e6e5b, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < 12134a652b0a10064844ea235173e70246eba6dc, >= 00cfd77b9063dcdf3628a7087faba60de85a9cc8 < b4cd80b0338945a94972ac3ed54f8338d2da2076, >= 5.10, >= 5.10 < 6.1.111, >= 6.2 < 6.6.52, >= 6.7 < 6.10.11, 6.11. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.1.111, 6.6.52, 6.10.11. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.