<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T00:28:12.848297+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2023-53565</id>
    <title>CVE-2023-53565 — wifi: brcmfmac: Check for probe() id argument being NULL</title>
    <updated>2026-10-04T00:28:12.865506+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: brcmfmac: Check for probe() id argument being NULL</p>
<p>The probe() id argument may be NULL in 2 scenarios:</p>
<p>1. brcmf_pcie_pm_leave_D3() calling brcmf_pcie_probe() to reprobe
   the device.</p>
<p>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.</p>
<p>1. Is being hit by users causing the following oops on resume and causing
wifi to stop working:</p>
<p>BUG: kernel NULL pointer dereference, address: 0000000000000018
&lt;snip&gt;
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]
&lt;snip&gt;
Call Trace:
 &lt;TASK&gt;
 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
&lt;snip&gt;</p>
<p>Fix this by checking for id being NULL.</p>
<p>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.</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53565"/>
  </entry>
</feed>
