CVE-2025-39952: wifi: wilc1000: avoid buffer overflow in WID string configuration
In the Linux kernel, the following vulnerability has been resolved:
wifi: wilc1000: avoid buffer overflow in WID string configuration
Fix the following copy overflow warning identified by Smatch checker.
drivers/net/wireless/microchip/wilc1000/wlancfg.c:184 wilcwlanparseresponseframe() error: 'memcpy()' 'cfg->s[i]->str' copy overflow (512 vs 65537)
This patch introduces size check before accessing the memory buffer. The checks are base on the WID type of received data from the firmware. For WID string configuration, the size limit is determined by individual element size in 'struct wilccfgstrvals' that is maintained in 'len' field of 'struct wilccfgstr'.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch wifi: wilc1000: avoid buffer overflow in WID string configuration - Compensating control
Apply the resolved change that introduces a size check before accessing the memory buffer in drivers/net/wireless/microchip/wilc1000/wlan_cfg.c (wilc_wlan_parse_response_frame()) for WID string configuration parsing.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-39952?
CVE-2025-39952 has been classified as a medium severity vulnerability due to the potential for a buffer overflow.
How do I fix CVE-2025-39952?
To fix CVE-2025-39952, upgrade to the patched version of the Linux kernel that includes the necessary updates to the wilc1000 driver.
What impact does CVE-2025-39952 have on systems running the Linux kernel?
CVE-2025-39952 can lead to buffer overflow, potentially resulting in system instability or unauthorized code execution on affected systems.
Which versions of the Linux kernel are affected by CVE-2025-39952?
CVE-2025-39952 affects various versions of the Linux kernel prior to the patch release that addresses the vulnerability.
Is CVE-2025-39952 being actively exploited?
As of now, there are no reports indicating that CVE-2025-39952 is being actively exploited in the wild.