CVE-2025-39952
What it is
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/wlan_cfg.c:184 wilc_wlan_parse_response_frame() 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 wilc_cfg_str_vals' that is maintained in 'len' field of 'struct wilc_cfg_str'.
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-787 · Out-of-bounds write
- Record status
- Modified
Affected
- Linux Kernel < 6.6.108
- Linux Kernel < 6.12.49
- Linux Kernel < 6.16.9
- Linux Kernel 6.17
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-39952.md and follow it. Check whether this project is affected by CVE-2025-39952. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2203ef417044b10a8563ade6a17c74183745d72e
- https://git.kernel.org/stable/c/6085291a1a5865d4ad70f0e5812d524ebd5d1711
- https://git.kernel.org/stable/c/ae50f8562306a7ea1cf3c9722f97ee244f974729
- https://git.kernel.org/stable/c/fe9e4d0c39311d0f97b024147a0d155333f388b5
References
- https://git.kernel.org/stable/c/2203ef417044b10a8563ade6a17c74183745d72e
- https://git.kernel.org/stable/c/5f1578a8684794318a60a022cedbffaa3dc444ce
- https://git.kernel.org/stable/c/6085291a1a5865d4ad70f0e5812d524ebd5d1711
- https://git.kernel.org/stable/c/ae50f8562306a7ea1cf3c9722f97ee244f974729
- https://git.kernel.org/stable/c/fe9e4d0c39311d0f97b024147a0d155333f388b5