Kernel stack disclosure via uncleared PMK structure
Published Oct 22, 2025 · Updated Oct 22, 2025
Information disclosure in Linux brcmfmac allows adjacent attackers to obtain uninitialized kernel stack contents through PMK setup. The brcmf_set_pmk function sends the full brcmf_wsec_pmk_le structure to device firmware without first clearing bytes left unwritten by PMK encoding. Exposure requires the brcmfmac driver and compatible Broadcom wireless hardware; the published impact is limited to confidentiality.
Summary
What happened
Information disclosure in Linux brcmfmac allows adjacent attackers to obtain uninitialized kernel stack contents through PMK setup. The brcmf_set_pmk function sends the full brcmf_wsec_pmk_le structure to device firmware without first clearing bytes left unwritten by PMK encoding. Exposure requires the brcmfmac driver and compatible Broadcom wireless hardware; the published impact is limited to confidentiality.
The record
- CVE
- CVE-2023-53715
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1687845eb8f37360a9ee849a3587ab659b090773
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2bc34facb90ceeff6f8c17d2006575a6d07c3825
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2fa3a5226b05e0a797c68b9609dcebe0cd236b27
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4e8dc0e5c7636efaadbd7e488acd34b4291c0431
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <56c7e9c39bd54fd753c0c4b1ed10278cbd3a5f02
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <89b89e52153fda2733562776c7c9d9d3ebf8dd6d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e242c66f7ecfe8f5b6eb308f4ea464fd8589c866
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f8a6c53ff1d91acd5a20eb627edbffd816eb9a4e
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo