Skip to content
Heist/ feed
Back to feed
UnratedFix available

wifi: ath10k: avoid NULL pointer error during sdio remove

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: avoid NULL pointer error during sdio remove When running 'rmmod ath10k', ath10k_sdio_remove() will free sdio workqueue by destroy_workqueue(). But if CONFIG_INIT_ON_FREE_DEFAULT_ON is set to yes, kernel panic will happen: Call trace: destroy_workqueue+0x1c/0x258 ath10k_sdio_remove+0x84/0x94 sdio_bus_remove+0x50/0x16c device_release_driver_internal+0x188/0x25c device_driver_detach+0x20/0x2c This is because during 'rmmod ath10k', ath10k_sdio_remove() will call ath10k_core_destroy() before destroy_workqueue(). wiphy_dev_release() will finally be called in ath10k_core_destroy(). This function will free struct cfg80211_registered_device *rdev and all its members, including wiphy, dev and the pointer of sdio workqueue. Then the pointer of sdio workqueue will be set to NULL due to CONFIG_INIT_ON_FREE_DEFAULT_ON. After device release, destroy_workqueue() will use NULL pointer then the kernel panic happen. Call trace: ath10k_sdio_remove ->ath10k_core_unregister …… ->ath10k_core_stop ->ath10k_hif_stop ->ath10k_sdio_irq_disable ->ath10k_hif_power_down ->del_timer_sync(&ar_sdio->sleep_timer) ->ath10k_core_destroy ->ath10k_mac_destroy ->ieee80211_free_hw ->wiphy_free …… ->wiphy_dev_release ->destroy_workqueue Need to call destroy_workqueue() before ath10k_core_destroy(), free the work queue buffer first and then free pointer of work queue by ath10k_core_destroy(). This order matches the error path order in a

Products
Kernel
Affected versions
Not specified
Fixed versions
5.10.237, 5.15.181, 6.1.127, 6.12.5, 6.6.70
CVEs
CVE-2024-56599
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 06:58 UTC · Revision 1

Source evidence

wifi: ath10k: avoid NULL pointer error during sdio remove

core-osv · Original source

Published 27 Dec 2024, 14:51 UTC

In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: avoid NULL pointer error during sdio remove When running 'rmmod ath10k', ath10k_sdio_remove() will free sdio workqueue by destroy_workqueue(). But if CONFIG_INIT_ON_FREE_DEFAULT_ON is set to yes, kernel panic will happen: Call trace: destroy_workqueue+0x1c/0x258 ath10k_sdio_remove+0x84/0x94 sdio_bus_remove+0x50/0x16c device_release_driver_internal+0x188/0x25c device_driver_detach+0x20/0x2c This is because during 'rmmod ath10k', ath10k_sdio_remove() will call ath10k_core_destroy() before destroy_workqueue(). wiphy_dev_release() will finally be called in ath10k_core_destroy(). This function will free struct cfg80211_registered_device *rdev and all its members, including wiphy, dev and the pointer of sdio workqueue. Then the pointer of sdio workqueue will be set to NULL due to CONFIG_INIT_ON_FREE_DEFAULT_ON. After device release, destroy_workqueue() will use NULL pointer then the kernel panic happen. Call trace: ath10k_sdio_remove ->ath10k_core_unregister …… ->ath10k_core_stop ->ath10k_hif_stop ->ath10k_sdio_irq_disable ->ath10k_hif_power_down ->del_timer_sync(&ar_sdio->sleep_timer) ->ath10k_core_destroy ->ath10k_mac_destroy ->ieee80211_free_hw ->wiphy_free …… ->wiphy_dev_release ->destroy_workqueue Need to call destroy_workqueue() before ath10k_core_destroy(), free the work queue buffer first and then free pointer of work queue by ath10k_core_destroy(). This order matches the error path order in a

osv:CVE-2024-56599

Kernel

Fixed versions: 5.10.237, 5.15.181, 6.1.127, 6.6.70, 6.12.5

Complete source record
{
  "id": "d3503742fa2a0c1dcbb7df8e64d517c63c086adccb7aa046164a817422e8920d",
  "url": "https://osv.dev/vulnerability/CVE-2024-56599",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "wifi: ath10k: avoid NULL pointer error during sdio remove",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: avoid NULL pointer error during sdio remove When running 'rmmod ath10k', ath10k_sdio_remove() will free sdio workqueue by destroy_workqueue(). But if CONFIG_INIT_ON_FREE_DEFAULT_ON is set to yes, kernel panic will happen: Call trace: destroy_workqueue+0x1c/0x258 ath10k_sdio_remove+0x84/0x94 sdio_bus_remove+0x50/0x16c device_release_driver_internal+0x188/0x25c device_driver_detach+0x20/0x2c This is because during 'rmmod ath10k', ath10k_sdio_remove() will call ath10k_core_destroy() before destroy_workqueue(). wiphy_dev_release() will finally be called in ath10k_core_destroy(). This function will free struct cfg80211_registered_device *rdev and all its members, including wiphy, dev and the pointer of sdio workqueue. Then the pointer of sdio workqueue will be set to NULL due to CONFIG_INIT_ON_FREE_DEFAULT_ON. After device release, destroy_workqueue() will use NULL pointer then the kernel panic happen. Call trace: ath10k_sdio_remove ->ath10k_core_unregister …… ->ath10k_core_stop ->ath10k_hif_stop ->ath10k_sdio_irq_disable ->ath10k_hif_power_down ->del_timer_sync(&ar_sdio->sleep_timer) ->ath10k_core_destroy ->ath10k_mac_destroy ->ieee80211_free_hw ->wiphy_free …… ->wiphy_dev_release ->destroy_workqueue Need to call destroy_workqueue() before ath10k_core_destroy(), free the work queue buffer first and then free pointer of work queue by ath10k_core_destroy(). This order matches the error path order in a",
    "evidence": "osv:CVE-2024-56599",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.10.237",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.181",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.127",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.70",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2024-56599",
      "aliases": [
        "CVE-2024-56599"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5"
                },
                {
                  "fixed": "27d5d217ae7ffb99dd623375a17a7d3418d9c755"
                },
                {
                  "fixed": "27fda36eedad9e4ec795dc481f307901d1885112"
                },
                {
                  "fixed": "6e5dbd1c04abf2c19b2282915e6fa48b6ccc6921"
                },
                {
                  "fixed": "b35de9e01fc79c7baac666fb2dcb4ba7698a1d97"
                },
                {
                  "fixed": "543c0924d446b21f35701ca084d7feca09511220"
                },
                {
                  "fixed": "95c38953cb1ecf40399a676a1f85dfe2b5780a9a"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56599.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "3.11.0"
                },
                {
                  "fixed": "5.10.237"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.181"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "6.1.127"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.70"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.5"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56599.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.857456539Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/27d5d217ae7ffb99dd623375a17a7d3418d9c755",
        "https://git.kernel.org/stable/c/27fda36eedad9e4ec795dc481f307901d1885112",
        "https://git.kernel.org/stable/c/543c0924d446b21f35701ca084d7feca09511220",
        "https://git.kernel.org/stable/c/6e5dbd1c04abf2c19b2282915e6fa48b6ccc6921",
        "https://git.kernel.org/stable/c/95c38953cb1ecf40399a676a1f85dfe2b5780a9a",
        "https://git.kernel.org/stable/c/b35de9e01fc79c7baac666fb2dcb4ba7698a1d97",
        "https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html",
        "https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56599.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-56599",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56599.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-56599",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 493193,
  "published_at": "2024-12-27T14:51:05.866+00:00"
}