{"vulnerability": "CVE-2024-56599", "sightings": [{"uuid": "55508858-ddda-44f0-ba2d-a0b2fb53cc28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56599", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbvhbdfe25", "content": "", "creation_timestamp": "2024-12-27T15:17:50.154197Z"}, {"uuid": "4e5dac36-7e88-4554-8aeb-15034a2c39f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56599", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2762", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-56599\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath10k: avoid NULL pointer error during sdio remove\n\nWhen running 'rmmod ath10k', ath10k_sdio_remove() will free sdio\nworkqueue by destroy_workqueue(). But if CONFIG_INIT_ON_FREE_DEFAULT_ON\nis set to yes, kernel panic will happen:\nCall trace:\n destroy_workqueue+0x1c/0x258\n ath10k_sdio_remove+0x84/0x94\n sdio_bus_remove+0x50/0x16c\n device_release_driver_internal+0x188/0x25c\n device_driver_detach+0x20/0x2c\n\nThis is because during 'rmmod ath10k', ath10k_sdio_remove() will call\nath10k_core_destroy() before destroy_workqueue(). wiphy_dev_release()\nwill finally be called in ath10k_core_destroy(). This function will free\nstruct cfg80211_registered_device *rdev and all its members, including\nwiphy, dev and the pointer of sdio workqueue. Then the pointer of sdio\nworkqueue will be set to NULL due to CONFIG_INIT_ON_FREE_DEFAULT_ON.\n\nAfter device release, destroy_workqueue() will use NULL pointer then the\nkernel panic happen.\n\nCall trace:\nath10k_sdio_remove\n  -&gt;ath10k_core_unregister\n    \u2026\u2026\n    -&gt;ath10k_core_stop\n      -&gt;ath10k_hif_stop\n        -&gt;ath10k_sdio_irq_disable\n    -&gt;ath10k_hif_power_down\n      -&gt;del_timer_sync(&amp;ar_sdio-&gt;sleep_timer)\n  -&gt;ath10k_core_destroy\n    -&gt;ath10k_mac_destroy\n      -&gt;ieee80211_free_hw\n        -&gt;wiphy_free\n    \u2026\u2026\n          -&gt;wiphy_dev_release\n  -&gt;destroy_workqueue\n\nNeed to call destroy_workqueue() before ath10k_core_destroy(), free\nthe work queue buffer first and then free pointer of work queue by\nath10k_core_destroy(). This order matches the error path order in\nath10k_sdio_probe().\n\nNo work will be queued on sdio workqueue between it is destroyed and\nath10k_core_destroy() is called. Based on the call_stack above, the\nreason is:\nOnly ath10k_sdio_sleep_timer_handler(), ath10k_sdio_hif_tx_sg() and\nath10k_sdio_irq_disable() will queue work on sdio workqueue.\nSleep timer will be deleted before ath10k_core_destroy() in\nath10k_hif_power_down().\nath10k_sdio_irq_disable() only be called in ath10k_hif_stop().\nath10k_core_unregister() will call ath10k_hif_power_down() to stop hif\nbus, so ath10k_sdio_hif_tx_sg() won't be called anymore.\n\nTested-on: QCA6174 hw3.2 SDIO WLAN.RMH.4.4.1-00189\n\ud83d\udccf Published: 2024-12-27T14:51:05.866Z\n\ud83d\udccf Modified: 2025-01-23T17:00:48.430Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6e5dbd1c04abf2c19b2282915e6fa48b6ccc6921\n2. https://git.kernel.org/stable/c/b35de9e01fc79c7baac666fb2dcb4ba7698a1d97\n3. https://git.kernel.org/stable/c/543c0924d446b21f35701ca084d7feca09511220\n4. https://git.kernel.org/stable/c/95c38953cb1ecf40399a676a1f85dfe2b5780a9a", "creation_timestamp": "2025-01-23T17:02:57.000000Z"}, {"uuid": "3692542d-863c-456d-b854-70ef13e87d7b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56599", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}]}