https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 28 May 2026 05:30:46 +0000 https://vulnerability.circl.lu/sighting/41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9/export {"uuid": "41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://t.me/cvedetector/5385", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45010 - Linux MPTCP Local Address Used Counter Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45010 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmptcp: pm: only mark 'subflow' endp as available \n \nAdding the following warning ... \n \n WARN_ON_ONCE(msk->pm.local_addr_used == 0) \n \n... before decrementing the local_addr_used counter helped to find a bug \nwhen running the \"remove single address\" subtest from the mptcp_join.sh \nselftests. \n \nRemoving a 'signal' endpoint will trigger the removal of all subflows \nlinked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with \nrm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used \ncounter, which is wrong in this case because this counter is linked to \n'subflow' endpoints, and here it is a 'signal' endpoint that is being \nremoved. \n \nNow, the counter is decremented, only if the ID is being used outside \nof mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and \nif the ID is not 0 -- local_addr_used is not taking into account these \nones. This marking of the ID as being available, and the decrement is \ndone no matter if a subflow using this ID is currently available, \nbecause the subflow could have been closed before. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:44.000000Z"} {"uuid": "41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://t.me/cvedetector/5385", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45010 - Linux MPTCP Local Address Used Counter Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45010 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmptcp: pm: only mark 'subflow' endp as available \n \nAdding the following warning ... \n \n WARN_ON_ONCE(msk->pm.local_addr_used == 0) \n \n... before decrementing the local_addr_used counter helped to find a bug \nwhen running the \"remove single address\" subtest from the mptcp_join.sh \nselftests. \n \nRemoving a 'signal' endpoint will trigger the removal of all subflows \nlinked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with \nrm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used \ncounter, which is wrong in this case because this counter is linked to \n'subflow' endpoints, and here it is a 'signal' endpoint that is being \nremoved. \n \nNow, the counter is decremented, only if the ID is being used outside \nof mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and \nif the ID is not 0 -- local_addr_used is not taking into account these \nones. This marking of the ID as being available, and the decrement is \ndone no matter if a subflow using this ID is currently available, \nbecause the subflow could have been closed before. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:44.000000Z"} https://vulnerability.circl.lu/sighting/41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9/export Wed, 11 Sep 2024 18:41:44 +0000 https://vulnerability.circl.lu/sighting/54a3f609-8875-4141-92a9-8e864d72095a/export {"uuid": "54a3f609-8875-4141-92a9-8e864d72095a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "54a3f609-8875-4141-92a9-8e864d72095a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://vulnerability.circl.lu/sighting/54a3f609-8875-4141-92a9-8e864d72095a/export Thu, 19 Mar 2026 00:00:00 +0000