<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 08 May 2026 18:36:13 +0000</lastBuildDate>
    <item>
      <title>c0bab13c-b62e-40c6-9b4d-db28215afbd8</title>
      <link>https://vulnerability.circl.lu/sighting/c0bab13c-b62e-40c6-9b4d-db28215afbd8/export</link>
      <description>{"uuid": "c0bab13c-b62e-40c6-9b4d-db28215afbd8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46858", "type": "seen", "source": "https://t.me/cvedetector/6526", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46858 - Linux MPTCP Uninitialized Pointer Access Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-46858 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmptcp: pm: Fix uaf in __timer_delete_sync  \n  \nThere are two paths to access mptcp_pm_del_add_timer, result in a race  \ncondition:  \n  \n     CPU1    CPU2  \n     ====                               ====  \n     net_rx_action  \n     napi_poll                          netlink_sendmsg  \n     __napi_poll                        netlink_unicast  \n     process_backlog                    netlink_unicast_kernel  \n     __netif_receive_skb                genl_rcv  \n     __netif_receive_skb_one_core       netlink_rcv_skb  \n     NF_HOOK                            genl_rcv_msg  \n     ip_local_deliver_finish            genl_family_rcv_msg  \n     ip_protocol_deliver_rcu            genl_family_rcv_msg_doit  \n     tcp_v4_rcv                         mptcp_pm_nl_flush_addrs_doit  \n     tcp_v4_do_rcv                      mptcp_nl_remove_addrs_list  \n     tcp_rcv_established                mptcp_pm_remove_addrs_and_subflows  \n     tcp_data_queue                     remove_anno_list_by_saddr  \n     mptcp_incoming_options             mptcp_pm_del_add_timer  \n     mptcp_pm_del_add_timer             kfree(entry)  \n  \nIn remove_anno_list_by_saddr(running on CPU2), after leaving the critical  \nzone protected by \"pm.lock\", the entry will be released, which leads to the  \noccurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1).  \n  \nKeeping a reference to add_timer inside the lock, and calling  \nsk_stop_timer_sync() with this reference, instead of \"entry-&amp;gt;add_timer\".  \n  \nMove list_del(&amp;amp;entry-&amp;gt;list) to mptcp_pm_del_add_timer and inside the pm lock,  \ndo not directly access any members of the entry outside the pm lock, which  \ncan avoid similar \"entry-&amp;gt;x\" uaf. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:34.000000Z"}</description>
      <content:encoded>{"uuid": "c0bab13c-b62e-40c6-9b4d-db28215afbd8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46858", "type": "seen", "source": "https://t.me/cvedetector/6526", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46858 - Linux MPTCP Uninitialized Pointer Access Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-46858 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmptcp: pm: Fix uaf in __timer_delete_sync  \n  \nThere are two paths to access mptcp_pm_del_add_timer, result in a race  \ncondition:  \n  \n     CPU1    CPU2  \n     ====                               ====  \n     net_rx_action  \n     napi_poll                          netlink_sendmsg  \n     __napi_poll                        netlink_unicast  \n     process_backlog                    netlink_unicast_kernel  \n     __netif_receive_skb                genl_rcv  \n     __netif_receive_skb_one_core       netlink_rcv_skb  \n     NF_HOOK                            genl_rcv_msg  \n     ip_local_deliver_finish            genl_family_rcv_msg  \n     ip_protocol_deliver_rcu            genl_family_rcv_msg_doit  \n     tcp_v4_rcv                         mptcp_pm_nl_flush_addrs_doit  \n     tcp_v4_do_rcv                      mptcp_nl_remove_addrs_list  \n     tcp_rcv_established                mptcp_pm_remove_addrs_and_subflows  \n     tcp_data_queue                     remove_anno_list_by_saddr  \n     mptcp_incoming_options             mptcp_pm_del_add_timer  \n     mptcp_pm_del_add_timer             kfree(entry)  \n  \nIn remove_anno_list_by_saddr(running on CPU2), after leaving the critical  \nzone protected by \"pm.lock\", the entry will be released, which leads to the  \noccurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1).  \n  \nKeeping a reference to add_timer inside the lock, and calling  \nsk_stop_timer_sync() with this reference, instead of \"entry-&amp;gt;add_timer\".  \n  \nMove list_del(&amp;amp;entry-&amp;gt;list) to mptcp_pm_del_add_timer and inside the pm lock,  \ndo not directly access any members of the entry outside the pm lock, which  \ncan avoid similar \"entry-&amp;gt;x\" uaf. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:34.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/c0bab13c-b62e-40c6-9b4d-db28215afbd8/export</guid>
      <pubDate>Fri, 27 Sep 2024 15:53:34 +0000</pubDate>
    </item>
  </channel>
</rss>
