CVE-2023-53565
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-03-21
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.4 |
| linux | linux_kernel | 6.4 |
| linux | linux_kernel | From 6.2 (inc) to 6.3.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's brcmfmac wifi driver where the probe() function's id argument can be NULL in certain scenarios, such as when the device is reprobed during resume or when a user manually binds the driver via sysfs. This leads to a NULL pointer dereference causing a kernel oops and the wifi to stop working. The fix involves checking if the id argument is NULL and handling it appropriately to prevent the crash.
How can this vulnerability impact me? :
If this vulnerability is triggered, it can cause the wifi functionality on affected devices to stop working due to a kernel crash (NULL pointer dereference). This can disrupt network connectivity, especially on devices using the affected brcmfmac driver, such as certain Dell XPS models.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for the specific NULL pointer dereference oops related to brcmf_pcie_probe. You can check the kernel log for messages like 'BUG: kernel NULL pointer dereference' involving brcmf_pcie_probe and brcmf_pcie_pm_leave_D3. Use commands such as 'dmesg | grep brcmf_pcie_probe' or 'journalctl -k | grep brcmf_pcie_probe' to look for these error messages indicating the issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, which includes the check for the probe() id argument being NULL. Until then, avoid manually binding the brcmfmac driver through sysfs to prevent triggering the NULL id argument scenario. Additionally, avoid suspending and resuming the device in ways that trigger brcmf_pcie_pm_leave_D3 reprobe calls.