LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53565: wifi: brcmfmac: Check for probe() id argument being NULL

In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Check for probe() id argument being NULL The probe() id argument may be NULL in 2 scenarios: 1. brcmf_pcie_pm_leave_D3() calling brcmf_pcie_probe() to reprobe the device. 2. If a user tries to manually bind the driver from sysfs then the sdio / pcie / usb probe() function gets called with NULL as id argument. 1. Is being hit by users causing the following oops on resume and causing wifi to stop working: BUG: kernel NULL pointer dereference, address: 0000000000000018 <snip> Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIDS 1.13.0 02/10/2020 Workgueue: events_unbound async_run_entry_fn RIP: 0010:brcmf_pcie_probe+Ox16b/0x7a0 [brcmfmac] <snip> Call Trace: <TASK> brcmf_pcie_pm_leave_D3+0xc5/8x1a0 [brcmfmac be3b4cefca451e190fa35be8f00db1bbec293887] ? pci_pm_resume+0x5b/0xf0 ? pci_legacy_resume+0x80/0x80 dpm_run_callback+0x47/0x150 device_resume+0xa2/0x1f0 async_resume+0x1d/0x30 <snip> Fix this by checking for id being NULL. In the PCI and USB cases try a manual lookup of the id so that manually binding the driver through sysfs and more importantly brcmf_pcie_probe() on resume will work. For the SDIO case there is no helper to do a manual sdio_device_id lookup, so just directly error out on a NULL id there.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash the Broadcom brcmfmac Wi-Fi driver when a device resumes from low power or is manually bound. The reported effect is a kernel oops and Wi-Fi stopping after resume. The public record does not show remote code execution, data theft, or active exploitation.

Executive priority

Treat as a reliability and availability patch for affected Linux wireless devices, not an emergency internet-facing vulnerability based on current evidence.

Technical view

brcmfmac probe paths could receive a NULL id argument from PCI resume reprobe or manual sysfs binding. The driver dereferenced that argument, causing a NULL pointer dereference. The fix adds NULL handling, manual ID lookup for PCI and USB paths, and an error path for SDIO.

Likely exposure

Most relevant to Linux endpoints, laptops, or embedded systems using Broadcom Wi-Fi with the brcmfmac driver and affected kernel builds. Exposure appears availability-focused and hardware-dependent.

Exploitation context

No KEV listing and no cited source in the bundle reports active exploitation. The described trigger is resume from D3 power state or local manual driver binding through sysfs, not a network-delivered attack.

Researcher notes

The source evidence is limited to the CVE record and kernel stable commits. No CVSS, CWE, exploitability analysis, or broader product advisory is provided in the bundle.

Mitigation direction

  • Update to a Linux kernel or distro package containing the stable brcmfmac fixes.
  • Prioritize affected fleets using Broadcom Wi-Fi and suspend/resume workflows.
  • Check distribution advisories for backported fixes matching these kernel commits.
  • Avoid unsupported local driver binding workflows on unpatched systems where practical.

Validation and detection

  • Inventory Linux kernel versions and identify hosts using the brcmfmac driver.
  • Check whether vendor kernel packages include the referenced stable commits.
  • Review kernel logs for brcmfmac NULL pointer oops during resume.
  • Test suspend and resume on representative Broadcom Wi-Fi hardware after patching.
Prepared
Confidence
medium
Sources
4

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-2023-53565 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
0ADP providers
3Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxda6d9c8ecd00e20218461007948f2b0a8e7fa242, da6d9c8ecd00e20218461007948f2b0a8e7fa242unaffected
LinuxLinux6.2, 0, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

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