Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53715wifi: brcmfmac: cfg80211: Pass the PMK in binary instead of hex

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: cfg80211: Pass the PMK in binary instead of hex Apparently the hex passphrase mechanism does not work on newer chips/firmware (e.g. BCM4387). It seems there was a simple way of passing it in binary all along, so use that and avoid the hexification. OpenBSD has been doing it like this from the beginning, so this should work on all chips. Also clear the structure before setting the PMK. This was leaking uninitialized stack contents to the device.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < 1687845eb8f37360a9ee849a3587ab659b090773
    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < 2bc34facb90ceeff6f8c17d2006575a6d07c3825
    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < 56c7e9c39bd54fd753c0c4b1ed10278cbd3a5f02
    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < 4e8dc0e5c7636efaadbd7e488acd34b4291c0431
    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < e242c66f7ecfe8f5b6eb308f4ea464fd8589c866
    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < f8a6c53ff1d91acd5a20eb627edbffd816eb9a4e
    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < 2fa3a5226b05e0a797c68b9609dcebe0cd236b27
    • affected b8a64f0e96c2b258321ee03975aeb0f5e88a055b – < 89b89e52153fda2733562776c7c9d9d3ebf8dd6d
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 4.14.316 – ≤ 4.14.*
    • unaffected 4.19.284 – ≤ 4.19.*
    • unaffected 5.4.244 – ≤ 5.4.*
    • unaffected 5.10.181 – ≤ 5.10.*
    • unaffected 5.15.113 – ≤ 5.15.*
    • unaffected 6.1.30 – ≤ 6.1.*
    • unaffected 6.3.4 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53715 badge
[![CVE-2023-53715](https://cveledger.app/badge/CVE-2023-53715.svg)](https://cveledger.app/cve/CVE-2023-53715)

Record last updated .