Skip to content
Noroxi
CVE-2024-56541· NVD / CVE Program· CNA Linux

wifi: ath12k: fix use-after-free in ath12k_dp_cc_cleanup()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 35be5018a2a4d1b07bdfcf957c81121d22d16355, bdb281103373fd80eb5c91cede1e115ba270b4e9, e5e15c8b42923bfb6c84d3d906a9965d9a0f111d.

Low priority for now. Upgrade to Linux Linux 35be5018a2a4d1b07bdfcf957c81121d22d16355, bdb281103373fd80eb5c91cede1e115ba270b4e9, e5e15c8b42923bfb6c84d3d906a9965d9a0f111d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix use-after-free in ath12k_dp_cc_cleanup() During ath12k module removal, in ath12k_core_deinit(), ath12k_mac_destroy() un-registers ah->hw from mac80211 and frees the ah->hw as well as all the ar's in it. After this ath12k_core_soc_destroy()-> ath12k_dp_free()-> ath12k_dp_cc_cleanup() tries to access one of the freed ar's from pending skb. This is because during mac destroy, driver failed to flush few data packets, which were accessed later in ath12k_dp_cc_cleanup() and freed, but using ar from the packet led to this use-after-free. BUG: KASAN: use-after-free in ath12k_dp_cc_cleanup.part.0+0x5e2/0xd40 [ath12k] Write of size 4 at addr ffff888150bd3514 by task modprobe/8926 CPU: 0 UID: 0 PID: 8926 Comm: modprobe Not tainted 6.11.0-rc2-wt-ath+ #1746 Hardware name: Intel(R) Client Systems NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0067.2021.0528.1339 05/28/2021 Call Trace: <TASK> dump_stack_lvl+0x7d/0xe0 print_address_description.constprop.0+0x33/0x3a0 print_report+0xb5/0x260 ? kasan_addr_to_slab+0x24/0x80 kasan_report+0xd8/0x110 ? ath12k_dp_cc_cleanup.part.0+0x5e2/0xd40 [ath12k] ? ath12k_dp_cc_cleanup.part.0+0x5e2/0xd40 [ath12k] kasan_check_range+0xf3/0x1a0 __kasan_check_write+0x14/0x20 ath12k_dp_cc_cleanup.part.0+0x5e2/0xd40 [ath12k] ath12k_dp_free+0x178/0x420 [ath12k] ath12k_core_stop+0x176/0x200 [ath12k] ath12k_core_deinit+0x13f/0x210 [ath12k] ath12k_pci_remove+0xad/0x1c0 [ath12k] pci_device_remove+0x9b/0x1b0 device_remove+0xbf/0x150 device_release_driver_internal+0x3c3/0x580 ? __kasan_check_read+0x11/0x20 driver_detach+0xc4/0x190 bus_remove_driver+0x130/0x2a0 driver_unregister+0x68/0x90 pci_unregister_driver+0x24/0x240 ? find_module_all+0x13e/0x1e0 ath12k_pci_exit+0x10/0x20 [ath12k] __do_sys_delete_module+0x32c/0x580 ? module_flags+0x2f0/0x2f0 ? kmem_cache_free+0xf0/0x410 ? __fput+0x56f/0xab0 ? __fput+0x56f/0xab0 ? debug_smp_processor_id+0x17/0x20 __x64_sys_delete_module+0x4f/0x70 x64_sys_call+0x522/0x9f0 do_syscall_64+0x64/0x130 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f8182c6ac8b Commit 24de1b7b231c ("wifi: ath12k: fix flush failure in recovery scenarios") added the change to decrement the pending packets count in case of recovery which make sense as ah->hw as well all ar's in it are intact during recovery, but during core deinit there is no use in decrementing packets count or waking up the empty waitq as the module is going to be removed also ar's from pending skb's can't be used and the packets should just be released back. To fix this, avoid accessing ar from skb->cb when driver is being unregistered. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.1.1-00214-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-56541

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.10 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.10affected
    • 24de1b7b231cf01d08d12db26e66b0c46253a7da and later · before e5e15c8b42923bfb6c84d3d906a9965d9a0f111daffected · git
    • 24de1b7b231cf01d08d12db26e66b0c46253a7da and later · before 35be5018a2a4d1b07bdfcf957c81121d22d16355affected · git
    • 24de1b7b231cf01d08d12db26e66b0c46253a7da and later · before bdb281103373fd80eb5c91cede1e115ba270b4e9affected · git
    • before 6.10not affected · semver
    • 6.11.11 and later · up to and including 6.11.*not affected · semver
    • 6.12.2 and later · up to and including 6.12.*not affected · semver
    • 6.13 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.3-16.12.3-1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_2before 1-150700.15.3.11-150700.15.3.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_2before 1-150700.1.5.11-150700.1.5.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-64kbbefore 6.4.0-150700.53.6.16.4.0-150700.53.6.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-defaultbefore 6.4.0-150700.53.6.16.4.0-150700.53.6.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-default-basebefore 6.4.0-150700.53.6.1.150700.17.6.16.4.0-150700.53.6.1.150700.17.6.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-sourcebefore 6.4.0-150700.53.6.16.4.0-150700.53.6.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-zfcpdumpbefore 6.4.0-150700.53.6.16.4.0-150700.53.6.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7kernel-docsbefore 6.4.0-150700.53.6.16.4.0-150700.53.6.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7kernel-obs-buildbefore 6.4.0-150700.53.6.16.4.0-150700.53.6.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7kernel-symsbefore 6.4.0-150700.53.6.16.4.0-150700.53.6.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP7kernel-azurebefore 6.4.0-150700.20.6.16.4.0-150700.20.6.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP7kernel-source-azurebefore 6.4.0-150700.20.6.16.4.0-150700.20.6.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP7kernel-syms-azurebefore 6.4.0-150700.20.6.16.4.0-150700.20.6.1
SUSE:Real Time Module 15 SP7kernel-rtbefore 6.4.0-150700.7.8.16.4.0-150700.7.8.1
SUSE:Real Time Module 15 SP7kernel-source-rtbefore 6.4.0-150700.7.8.16.4.0-150700.7.8.1
SUSE:Real Time Module 15 SP7kernel-syms-rtbefore 6.4.0-150700.7.8.16.4.0-150700.7.8.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-56539Dec 27, 2024 · wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan()
    22Monitor
  • ← EarlierCVE-2024-56540Dec 27, 2024 · accel/ivpu: Prevent recovery invocation during probe and resume
    18Monitor
  • Later →CVE-2024-56542Dec 27, 2024 · drm/amd/display: fix a memleak issue when driver is removed
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux35be5018a2a4d1b07bdfcf957c81121d22d16355Vendor (CNA)
Linux Linuxbdb281103373fd80eb5c91cede1e115ba270b4e9Vendor (CNA)
Linux Linuxe5e15c8b42923bfb6c84d3d906a9965d9a0f111dVendor (CNA)
debian:linux6.12.3-1 · Debian:13Package registry (OSV)
suse:kernel-64kb6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-azure6.4.0-150700.20.6.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP7Package registry (OSV)
suse:kernel-default6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-default-base6.4.0-150700.53.6.1.150700.17.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-docs6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7_Update_21-150700.15.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-obs-build6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-source6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-source-azure6.4.0-150700.20.6.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP7Package registry (OSV)
suse:kernel-syms6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-syms-azure6.4.0-150700.20.6.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP7Package registry (OSV)
suse:kernel-zfcpdump6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records