CVE-2026-68192

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.

CVSS 3.1

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

EPSS

0.4% chance of exploitation in the next 30 days; higher than 34% of CVEs (scores of 2026-10-25)

CWE

CWE-415

Published

2026-08-10

Modified

2026-10-19

Record from

the NVD, synced 2026-10-21

References

• https://git.kernel.org/stable/c/044fca8f45ba9ab6ca526163155234cf88287ff5
• https://git.kernel.org/stable/c/0ca80328df23f851c86866720d4977783c919ee6
• https://git.kernel.org/stable/c/382ee00b2d1e31869ae576a60d3fbe7a2153512f
• https://git.kernel.org/stable/c/538c51e9d124cf656f2dd0c0394a8545efc7102d
• https://git.kernel.org/stable/c/5a045c2f0fbf029873d2295178fa0785ade35af0

Check your stackJSON