{"vulnerability": "cve-2024-57898", "sightings": [{"uuid": "26d045cc-61f1-4243-83ee-cbc6b8e77154", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtzdgdkr2b", "content": "", "creation_timestamp": "2025-01-15T13:17:08.449826Z"}, {"uuid": "065a2d77-cb1b-4593-9474-a5071fcede84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lfrvq5ymqx2u", "content": "", "creation_timestamp": "2025-01-15T13:47:48.494050Z"}, {"uuid": "ff309b4c-aa1e-45d2-80b4-db4c2b60aa26", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "23ab34a3-4db4-405b-a37e-2714d7fc2101", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "ab739760-dcb0-435b-afef-81cf719d2318", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1753", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57898\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: clear link ID from bitmap during link delete after clean up\n\nCurrently, during link deletion, the link ID is first removed from the\nvalid_links bitmap before performing any clean-up operations. However, some\nfunctions require the link ID to remain in the valid_links bitmap. One\nsuch example is cfg80211_cac_event(). The flow is -\n\nnl80211_remove_link()\n    cfg80211_remove_link()\n        ieee80211_del_intf_link()\n            ieee80211_vif_set_links()\n                ieee80211_vif_update_links()\n                    ieee80211_link_stop()\n                        cfg80211_cac_event()\n\ncfg80211_cac_event() requires link ID to be present but it is cleared\nalready in cfg80211_remove_link(). Ultimately, WARN_ON() is hit.\n\nTherefore, clear the link ID from the bitmap only after completing the link\nclean-up.\n\ud83d\udccf Published: 2025-01-15T13:05:49.718Z\n\ud83d\udccf Modified: 2025-01-15T13:05:49.718Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ae07daf440d3220d0986e676317a5da66e4f9dfd\n2. https://git.kernel.org/stable/c/b5c32ff6a3a38c74facdd1fe34c0d709a55527fd", "creation_timestamp": "2025-01-15T14:22:18.000000Z"}, {"uuid": "40e70526-ffaa-499e-a585-7e1f3c17e322", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://t.me/cvedetector/15445", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57898 - Linux Kernel wifi cfg80211 Link ID Information Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57898 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: cfg80211: clear link ID from bitmap during link delete after clean up  \n  \nCurrently, during link deletion, the link ID is first removed from the  \nvalid_links bitmap before performing any clean-up operations. However, some  \nfunctions require the link ID to remain in the valid_links bitmap. One  \nsuch example is cfg80211_cac_event(). The flow is -  \n  \nnl80211_remove_link()  \n    cfg80211_remove_link()  \n        ieee80211_del_intf_link()  \n            ieee80211_vif_set_links()  \n                ieee80211_vif_update_links()  \n                    ieee80211_link_stop()  \n                        cfg80211_cac_event()  \n  \ncfg80211_cac_event() requires link ID to be present but it is cleared  \nalready in cfg80211_remove_link(). Ultimately, WARN_ON() is hit.  \n  \nTherefore, clear the link ID from the bitmap only after completing the link  \nclean-up. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:06:47.000000Z"}]}