https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sun, 10 May 2026 10:54:35 +0000 https://vulnerability.circl.lu/sighting/508286e1-65ab-48ac-ac05-53e5adba1e01/export {"uuid": "508286e1-65ab-48ac-ac05-53e5adba1e01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57991", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14774", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57991\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: chan: fix soft lockup in rtw89_entity_recalc_mgnt_roles()\n\nDuring rtw89_entity_recalc_mgnt_roles(), there is a normalizing process\nwhich will re-order the list if an entry with target pattern is found.\nAnd once one is found, should have aborted the list_for_each_entry. But,\n`break` just aborted the inner for-loop. The outer list_for_each_entry\nstill continues. Normally, only the first entry will match the target\npattern, and the re-ordering will change nothing, so there won't be\nsoft lockup. However, in some special cases, soft lockup would happen.\n\nFix it by `goto fill` to break from the list_for_each_entry.\n\nThe following is a sample of kernel log for this problem.\n\nwatchdog: BUG: soft lockup - CPU#1 stuck for 26s! [wpa_supplicant:2055]\n[...]\nRIP: 0010:rtw89_entity_recalc ([...] chan.c:392 chan.c:479) rtw89_core\n[...]\n\ud83d\udccf Published: 2025-02-27T02:07:13.668Z\n\ud83d\udccf Modified: 2025-05-04T10:07:52.679Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/223ba95fdcd3c6090e2bd51dce66abb6dd4f9df9\n2. https://git.kernel.org/stable/c/01d2d34e9fcc9897081c3c16a666f793c8a38c58\n3. https://git.kernel.org/stable/c/e4790b3e314a4814f1680a5dc552031fb199b878", "creation_timestamp": "2025-05-04T10:18:14.000000Z"} {"uuid": "508286e1-65ab-48ac-ac05-53e5adba1e01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57991", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14774", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57991\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: chan: fix soft lockup in rtw89_entity_recalc_mgnt_roles()\n\nDuring rtw89_entity_recalc_mgnt_roles(), there is a normalizing process\nwhich will re-order the list if an entry with target pattern is found.\nAnd once one is found, should have aborted the list_for_each_entry. But,\n`break` just aborted the inner for-loop. The outer list_for_each_entry\nstill continues. Normally, only the first entry will match the target\npattern, and the re-ordering will change nothing, so there won't be\nsoft lockup. However, in some special cases, soft lockup would happen.\n\nFix it by `goto fill` to break from the list_for_each_entry.\n\nThe following is a sample of kernel log for this problem.\n\nwatchdog: BUG: soft lockup - CPU#1 stuck for 26s! [wpa_supplicant:2055]\n[...]\nRIP: 0010:rtw89_entity_recalc ([...] chan.c:392 chan.c:479) rtw89_core\n[...]\n\ud83d\udccf Published: 2025-02-27T02:07:13.668Z\n\ud83d\udccf Modified: 2025-05-04T10:07:52.679Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/223ba95fdcd3c6090e2bd51dce66abb6dd4f9df9\n2. https://git.kernel.org/stable/c/01d2d34e9fcc9897081c3c16a666f793c8a38c58\n3. https://git.kernel.org/stable/c/e4790b3e314a4814f1680a5dc552031fb199b878", "creation_timestamp": "2025-05-04T10:18:14.000000Z"} https://vulnerability.circl.lu/sighting/508286e1-65ab-48ac-ac05-53e5adba1e01/export Sun, 04 May 2025 10:18:14 +0000