wifi: brcmfmac: make release_scratchbuffers idempotent
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux 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 Linux
5.2
- KernelLinux
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
References 8
git.kernel.org
- stable/c/81c58a206d1deee01f4c29236d4154c0872f2a38
- stable/c/382ee00b2d1e31869ae576a60d3fbe7a2153512f
- stable/c/739b686aecdb14a6065300ea53401f043e51fd22
- stable/c/b7d1d8cb1bdca56aecebacd2896615da0acc126a
- stable/c/5a045c2f0fbf029873d2295178fa0785ade35af0
- stable/c/044fca8f45ba9ab6ca526163155234cf88287ff5
- stable/c/0ca80328df23f851c86866720d4977783c919ee6
- stable/c/538c51e9d124cf656f2dd0c0394a8545efc7102d