CVE-2024-56599

Aliases:UBUNTU-CVE-2024-56599DEBIAN-CVE-2024-56599
Advisory lineage Upstream: 0 Downstream: 56
Modified
Published: 27 Dec 2024, 14:51
Last modified:11 May 2026, 20:55

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.23% LOW
0% probability +0.15%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

27 Dec 2024, 14:51
Published
Vulnerability first disclosed
11 May 2026, 20:55
Last Modified
Vulnerability information updated

Description

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 ath10k_sdio_probe(). No work will be queued on sdio workqueue between it is destroyed and ath10k_core_destroy() is called. Based on the call_stack above, the reason is: Only ath10k_sdio_sleep_timer_handler(), ath10k_sdio_hif_tx_sg() and ath10k_sdio_irq_disable() will queue work on sdio workqueue. Sleep timer will be deleted before ath10k_core_destroy() in ath10k_hif_power_down(). ath10k_sdio_irq_disable() only be called in ath10k_hif_stop(). ath10k_core_unregister() will call ath10k_hif_power_down() to stop hif bus, so ath10k_sdio_hif_tx_sg() won't be called anymore. Tested-on: QCA6174 hw3.2 SDIO WLAN.RMH.4.4.1-00189

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.23%• Percentile: 15%

Techniques & Countermeasures

  • CWE-476•NULL Pointer Dereference

    The product dereferences a pointer that it expects to be valid but is NULL.

Affected Systems

  • debian•linux

    < 5.10.237-1 | < 6.1.128-1 | < 6.12.5-1 | < 6.12.5-1

  • debian•linux-6.1

    < 6.1.128-1~deb11u1

  • ubuntu•linux

    < 5.4.0-216.236 | < 5.15.0-140.150 | < 6.8.0-58.60

  • ubuntu•linux-allwinner-5.19

    all

  • ubuntu•linux-aws

    all | < 5.4.0-1146.156 | < 5.15.0-1084.91 | < 6.8.0-1027.29

  • ubuntu•linux-aws-5.0

    all

  • ubuntu•linux-aws-5.11

    all

  • ubuntu•linux-aws-5.13

    all

  • ubuntu•linux-aws-5.15

    < 5.15.0-1084.91~20.04.1

  • ubuntu•linux-aws-5.19

    all

  • ubuntu•linux-aws-5.3

    all

  • ubuntu•linux-aws-5.4

    < 5.4.0-1146.156~18.04.1

  • ubuntu•linux-aws-5.8

    all

  • ubuntu•linux-aws-6.2

    all

  • ubuntu•linux-aws-6.5

    all

  • ubuntu•linux-aws-6.8

    < 6.8.0-1027.29~22.04.1

  • ubuntu•linux-aws-fips

    all | < 5.4.0-1146.156+fips1 | < 5.15.0-1084.91+fips1

  • ubuntu•linux-aws-hwe

    all

  • ubuntu•linux-azure

    all | all | < 5.4.0-1151.158 | < 5.15.0-1089.98 | < 6.8.0-1027.32

  • ubuntu•linux-azure-4.15

    all

  • ubuntu•linux-azure-5.11

    all

  • ubuntu•linux-azure-5.13

    all

  • ubuntu•linux-azure-5.15

    < 5.15.0-1089.98~20.04.1

  • ubuntu•linux-azure-5.19

    all

  • ubuntu•linux-azure-5.3

    all

  • ubuntu•linux-azure-5.4

    < 5.4.0-1151.158~18.04.1

  • ubuntu•linux-azure-5.8

    all

  • ubuntu•linux-azure-6.11

    < 6.11.0-1012.12~24.04.1

  • ubuntu•linux-azure-6.2

    all

  • ubuntu•linux-azure-6.5

    all

  • ubuntu•linux-azure-6.8

    < 6.8.0-1027.32~22.04.1

  • ubuntu•linux-azure-edge

    all

  • ubuntu•linux-azure-fde

    all | all

  • ubuntu•linux-azure-fde-5.19

    all

  • ubuntu•linux-azure-fde-6.2

    all

  • ubuntu•linux-azure-fips

    all | < 5.4.0-1151.158+fips1 | < 5.15.0-1089.98+fips1

  • ubuntu•linux-azure-nvidia

    < 6.8.0-1014.15

  • ubuntu•linux-bluefield

    all | < 5.4.0-1105.112 | < 5.15.0-1066.68

  • ubuntu•linux-fips

    all | < 5.4.0-1120.130 | < 5.15.0-140.150+fips1 | < 6.8.0-78.78+fips1

  • ubuntu•linux-gcp

    all | all | < 5.4.0-1149.158 | < 5.15.0-1083.92 | < 6.8.0-1028.30

  • ubuntu•linux-gcp-4.15

    all

  • ubuntu•linux-gcp-5.11

    all

  • ubuntu•linux-gcp-5.13

    all

  • ubuntu•linux-gcp-5.15

    < 5.15.0-1083.92~20.04.1

  • ubuntu•linux-gcp-5.19

    all

  • ubuntu•linux-gcp-5.3

    all

  • ubuntu•linux-gcp-5.4

    < 5.4.0-1149.158~18.04.1

  • ubuntu•linux-gcp-5.8

    all

  • ubuntu•linux-gcp-6.11

    < 6.11.0-1011.11~24.04.1

  • ubuntu•linux-gcp-6.2

    all

Showing first 50 affected entries in server-rendered view.

References (56)