CVE-2026-68192

wifi: brcmfmac: make release_scratchbuffers idempotent

HIGH
8.8
CVSS Score
Published: August 10, 2026 at 12:00 PM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: make release_scratchbuffers idempotent brcmf_pcie_release_scratchbuffers() frees the shared.scratch and shared.ringupd DMA buffers with dma_free_coherent() but does not clear the pointers afterwards, unlike the sibling release_ringbuffers() which NULLs commonrings/flowrings/idxbuf on release. Both the bus_reset .reset callback (brcmf_pcie_reset) and brcmf_pcie_remove() call release_scratchbuffers. When reset teardown has run before removal, remove's own teardown would call dma_free_coherent() a second time on the already-freed DMA allocation. NULL the pointers after free, matching release_ringbuffers(), so a later release observes that the allocation has already been released. This patch makes repeated sequential release safe; the reset-work lifetime is handled separately by the following patch. This issue was found by an in-house static analysis tool.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4684997d9eea29380000e062755aa6d368d789a35.2
Vendor states this is fixed in 044fca8f45ba9ab6ca526163155234cf88287ff5 (fixed)
Vendor states this is fixed in 0ca80328df23f851c86866720d4977783c919ee6 (fixed)
Vendor states this is fixed in 382ee00b2d1e31869ae576a60d3fbe7a2153512f (fixed)
Vendor states this is fixed in 538c51e9d124cf656f2dd0c0394a8545efc7102d (fixed)
Vendor states this is fixed in 5a045c2f0fbf029873d2295178fa0785ade35af0 (fixed)
Vendor states this is fixed in 739b686aecdb14a6065300ea53401f043e51fd22 (fixed)
Vendor states this is fixed in 81c58a206d1deee01f4c29236d4154c0872f2a38 (fixed)
Vendor states this is fixed in b7d1d8cb1bdca56aecebacd2896615da0acc126a (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.2 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-415

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card