CVE-2023-53582
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-03-23
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.15 (inc) to 4.19.276 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.235 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.173 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.99 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.16 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.3 (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 is a stack-out-of-bounds read in the Linux kernel's brcmfmac driver. It occurs when a buffer containing a CLM version string is not properly null-terminated before being passed to the strreplace() function. This can lead to reading beyond the intended memory boundary on the stack, which is a form of memory safety issue. The problem arises because the buffer is filled by memcpy() but not ensured to be null-terminated, causing strreplace() to potentially read past the buffer's end.
How can this vulnerability impact me? :
The stack-out-of-bounds read could lead to undefined behavior in the kernel, including potential crashes or information leakage. Since it involves reading memory beyond the intended buffer, it might expose sensitive data or cause system instability. This could impact the reliability and security of devices using the affected brcmfmac wireless driver.
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 messages related to brcmfmac errors or KASAN stack-out-of-bounds reports, such as lines containing 'brcmfmac: brcmf_c_process_clm_blob: no clm_blob available' or 'BUG: KASAN: stack-out-of-bounds in strreplace'. You can use commands like 'dmesg | grep brcmfmac' or 'journalctl -k | grep brcmfmac' to check for these messages.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is fixed, ensuring that the brcmfmac driver includes the patch that null-terminates the CLM version string to prevent stack-out-of-bounds reads. If updating is not immediately possible, consider disabling or unloading the brcmfmac driver to prevent triggering the vulnerable code.