CVE-2022-50258
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-11-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
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 ('buf') that is not null-terminated is passed to the strsep() function in the brcmf_c_preinit_dcmds() function. The buffer is supposed to contain a firmware version string copied by memcpy(), but without proper null-termination, strsep() can read beyond the buffer's boundary, causing a potential memory safety issue. The patch fixes this by ensuring the buffer is null-terminated.
How can this vulnerability impact me? :
This vulnerability can lead to a stack-out-of-bounds read in the kernel, which may cause system instability, crashes, or potentially expose sensitive kernel memory. While the description does not specify exploitation details, such memory safety issues can be leveraged for denial of service or privilege escalation attacks depending on the context.