Answer in brief
CVE-2026-68192 records a Unknown severity vulnerability in wifi: brcmfmac: make release_scratchbuffers idempotent. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4684997d9eea29380000e062755aa6d368d789a3 <b7d1d8cb1bdca56aecebacd2896615da0acc126a || >=4684997d9eea29380000e062755aa6d368d789a3 <5a045c2f0fbf029873d2295178fa0785ade35af0 || >=4684997d9eea29380000e062755aa6d368d789a3 <044fca8f45ba9ab6ca526163155234cf88287ff5 || >=4684997d9eea29380000e062755aa6d368d789a3 <0ca80328df23f851c86866720d4977783c919ee6 || >=4684997d9eea29380000e062755aa6d368d789a3 <538c51e9d124cf656f2dd0c0394a8545efc7102d | b7d1d8cb1bdca56aecebacd2896615da0acc126a, 5a045c2f0fbf029873d2295178fa0785ade35af0, 044fca8f45ba9ab6ca526163155234cf88287ff5, 0ca80328df23f851c86866720d4977783c919ee6, 538c51e9d124cf656f2dd0c0394a8545efc7102d |
| Linux/Linuxgeneric | 5.2 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68192 records a Unknown severity vulnerability in wifi: brcmfmac: make release_scratchbuffers idempotent. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4684997d9eea29380000e062755aa6d368d789a3 <b7d1d8cb1bdca56aecebacd2896615da0acc126a || >=4684997d9eea29380000e062755aa6d368d789a3 <5a045c2f0fbf029873d2295178fa0785ade35af0 || >=4684997d9eea29380000e062755aa6d368d789a3 <044fca8f45ba9ab6ca526163155234cf88287ff5 || >=4684997d9eea29380000e062755aa6d368d789a3 <0ca80328df23f851c86866720d4977783c919ee6 || >=4684997d9eea29380000e062755aa6d368d789a3 <538c51e9d124cf656f2dd0c0394a8545efc7102d | b7d1d8cb1bdca56aecebacd2896615da0acc126a, 5a045c2f0fbf029873d2295178fa0785ade35af0, 044fca8f45ba9ab6ca526163155234cf88287ff5, 0ca80328df23f851c86866720d4977783c919ee6, 538c51e9d124cf656f2dd0c0394a8545efc7102d |
| Linux/Linuxgeneric | 5.2 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.