LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38575: wifi: brcmfmac: pcie: handle randbuf allocation failure

In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: pcie: handle randbuf allocation failure The kzalloc() in brcmf_pcie_download_fw_nvram() will return null if the physical memory has run out. As a result, if we use get_random_bytes() to generate random bytes in the randbuf, the null pointer dereference bug will happen. In order to prevent allocation failure, this patch adds a separate function using buffer on kernel stack to generate random bytes in the randbuf, which could prevent the kernel stack from overflow.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems if the Broadcom brcmfmac PCIe Wi-Fi driver hits a memory allocation failure while preparing firmware/NVRAM data. The business impact is mainly availability risk on systems using that driver, not confirmed data theft or remote compromise.

Executive priority

Treat this as a targeted kernel availability issue. Patch affected Linux systems through normal kernel maintenance, with faster handling for Broadcom Wi-Fi endpoints in operationally sensitive environments.

Technical view

CVE-2024-38575 is a null pointer dereference in brcmf_pcie_download_fw_nvram(). If kzalloc() fails, get_random_bytes() can operate on a null randbuf. The kernel fix changes random-byte generation to use a separate stack-buffer helper, avoiding this allocation-failure path.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds with the Broadcom brcmfmac PCIe Wi-Fi driver. Exact exposure depends on distribution backports, hardware presence, and whether the referenced stable fixes are included.

Exploitation context

The source bundle says CISA KEV is false and provides no evidence of active exploitation. Triggerability appears tied to memory exhaustion during brcmfmac PCIe firmware/NVRAM handling; practical exploitability is not established in the provided sources.

Researcher notes

The CVE record lacks CVSS, CWE, and exploit details. Version data in the bundle is incomplete and distribution backports may differ, so validation should focus on kernel build provenance and the specific brcmfmac PCIe fix.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Check distribution advisories for patched kernel packages and backport status.
  • Prioritize laptops, appliances, or embedded systems using Broadcom PCIe Wi-Fi.
  • If no patch is available, monitor vendor guidance for mitigations.
  • Avoid inventing workarounds not documented by the kernel or distribution vendor.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Identify systems loading or packaging the brcmfmac PCIe Wi-Fi driver.
  • Confirm patched source or package includes the CVE-2024-38575 stable commit.
  • Review vendor changelogs for this CVE or the randbuf allocation fix.
  • After updating, confirm the running kernel matches the patched package.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-38575 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc35105f375b530bc27e03ea9250b1c26dd4cae86, 91918ce88d9fef408bb12c46a27c73d79b604c20, 91918ce88d9fef408bb12c46a27c73d79b604c20, 91918ce88d9fef408bb12c46a27c73d79b604c20, 91918ce88d9fef408bb12c46a27c73d79b604c20, ba72baed066f3bfa8b489e4b58f1fcaf51c04f83unaffected
LinuxLinux6.4, 0, 6.1.93, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.