cve.bz

CVE-2026-64586 linux linux: Use After Free

8.8 highEPSS 0.2%Fix available

High (8.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: drain bus_reset work on device removal brcmf_fw_crashed() and the debugfs "reset" entry both schedule drvr->bus_reset, whose callback recovers drvr through container_of() and dereferences it. The removal path frees drvr (brcmf_free -> wiphy_free) without draining the work, so a bus_reset callback pending or running during removal can outlive drvr. Cancellation cannot live in brcmf_detach() or brcmf_free(): the work callback reaches teardown through the bus .reset op (PCIe brcmf_pcie_reset -> brcmf_detach; SDIO brcmf_sdio_bus_reset -> brcmf_sdiod_remove -> brcmf_free), so cancelling there would wait for the running work and deadlock. Add a per-bus mutex (bus_reset_lock) and route all arming through brcmf_bus_schedule_reset(), which under the lock skips when the bus is marked removing. Each bus remove entry calls brcmf_bus_cancel_reset_work(), which under the same lock sets removing and cancels the work. Holding the mutex across cancel_work_sync() makes the set-removing + drain step atomic. Every producer reaches the arming path from process context -- the PCIe firmware-halt notification runs in the threaded IRQ handler (brcmf_pcie_isr_thread) and the SDIO hostmail path runs from the data workqueue -- so the mutex is taken only in sleepable contexts. Where applicable the remove entry first stops the firmware-crash producer: on PCIe mask the mailbox and synchronize_irq; on SDIO unregister the bus interrupt and cancel the data worker, which also reports firmware halts through brcmf_fw_crashed(). The mutex is initialized at bus allocation. The SDIO suspend power-off path frees drvr through the same brcmf_sdiod_remove() and takes the same lock; resume re-allows the work only on a successful re-probe. Also guard brcmf_fw_crashed() against a NULL bus_if/drvr: it can fire before brcmf_attach() wires up drvr, and it dereferences drvr (bphy_err/brcmf_dev_coredump) before reaching the arming gate. The bus_reset work is shared across buses, so the drain is applied to every remove path: PCIe (the .reset op introduced by the Fixes commit), SDIO (arms the same work through brcmf_fw_crashed()), and USB (via the debugfs "reset" entry). cancel_work_sync() drains a running or pending bus_reset work item before removal frees drvr, and patch 1/2 makes the scratch-buffer release safe when reset teardown has already released those DMA buffers. This patch fixes the lifetime of the bus_reset work item itself. It does not attempt to address the separate, pre-existing lifetime of the asynchronous firmware completion started by the PCIe reset path. That callback needs its own lifetime/ownership protocol and is being tracked separately. This issue was found by an in-house static analysis tool.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.266
  • Linux Linux: fixed in 5.15.217
  • Linux Linux: fixed in 6.1.184
  • Linux Linux: fixed in 6.6.151
  • Linux Linux: fixed in 6.12.103
  • Linux Linux: fixed in 6.18.44
  • Linux Linux: fixed in 7.1.6
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-64586 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64586?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64586?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64586 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.2 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.266
Linux5.155.15.217
Linux6.16.1.184
Linux6.66.6.151
Linux6.126.12.103
Linux6.186.18.44
Linux7.17.1.6
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.187-1DEBIAN-CVE-2026-64586
Debian12linux-6.126.12.107-1~deb12u1DEBIAN-CVE-2026-64586
Debian13linux6.12.105-1DEBIAN-CVE-2026-64586
Debian14linux7.1.6-1DEBIAN-CVE-2026-64586
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-64586
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-64586
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-64586
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-64586 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-64586 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-64586 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-64586 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-64586 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-64586
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-64586 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-64586 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-64586 USN-9024-1
80 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.38.1SUSE-SU-2026:23897-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.38.1SUSE-SU-2026:23902-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.38.1.160000.2.23SUSE-SU-2026:23902-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.38.1.160000.2.23SUSE-SU-2026:23887-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.38.1SUSE-SU-2026:23887-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.38.1SUSE-SU-2026:23881-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.38.1.160000.2.22openSUSE-SU-2026:21910-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.38.1openSUSE-SU-2026:21910-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
openSUSETumbleweedkernel-source7.1.7-1.1openSUSE-SU-2026:11476-1
Azure Linux3kernel6.6.152.1-1AZL-94551
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-64586
Alpaquita25linux-lts6.12.103-r0BELL-CVE-2026-64586
Alpaquitastreamlinux-lts6.18.46-r0BELL-CVE-2026-64586

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A use-after-free can occur in brcmfmac because the shared bus_reset work item may remain pending or running while device removal frees the drvr object through brcmf_free and wiphy_free. The bus_reset callback recovers drvr with container_of and dereferences it, so a reset armed by brcmf_fw_crashed or debugfs reset can outlive the object lifetime during PCIe, SDIO, or USB removal. For the CVSS the PR:L is used in the paranoid score because some deployments may expose reset, hotplug, suspend, or firmware crash triggering to a local service account, container root, or otherwise reduced local privilege rather than only full administrator control. The issue is not directly network reachable as AV:N from the patch context. A wireless adjacent contribution through a firmware crash producer is possible only as a device specific hypothesis and should not be treated as the primary vector without more evidence. Impact is at least local denial of service via kernel crash.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-64586.

References

Check your stackJSON