LiveActive security incident?Get immediate response
CVE Record

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/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'.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux’s Microchip WILC1000 Wi-Fi driver can copy oversized firmware configuration data into a smaller buffer. On systems using this driver, the resulting memory corruption could compromise confidentiality, integrity, or availability. Systems without the WILC1000 driver or hardware are unlikely to be exposed.

Executive priority

Treat as high priority for confirmed WILC1000 deployments because successful memory corruption could affect all three security objectives without authentication or user action. First establish whether the hardware and driver exist; systems outside that scope do not warrant emergency remediation for this CVE alone.

Technical view

The vulnerable wilc_wlan_parse_response_frame() path in drivers/net/wireless/microchip/wilc1000/wlan_cfg.c failed to validate WID string lengths before copying firmware response data. The kernel fix applies type-specific bounds checks using each configuration element’s maintained length. CVSS 3.1 rates the issue 8.8 with adjacent access, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is concentrated in Linux-based embedded, IoT, or appliance systems using Microchip WILC1000 Wi-Fi hardware and the affected driver. The supplied version data identifies affected releases but is insufficient to establish every vulnerable distribution kernel or backport. Confirm patch status with the kernel or device vendor.

Exploitation context

The CVSS vector describes an adjacent attacker with low attack complexity, requiring neither privileges nor user interaction. The vulnerable input is received from firmware. The bundle does not establish a practical attack path, public proof of concept, or active exploitation, and the CVE is not listed as KEV.

Researcher notes

The source documents a Smatch-detected copy overflow and four stable-kernel fix commits. It does not identify a CWE, demonstrated exploit, affected distribution packages, or confirmed exploitation. The repeated commit identifiers and sparse version list should not be interpreted as a complete distribution-level applicability matrix.

Mitigation direction

  • Inventory devices using Microchip WILC1000 Wi-Fi hardware or the wilc1000 Linux driver.
  • Obtain a vendor-supported kernel containing the applicable referenced stable fix.
  • Prioritize embedded or remotely managed devices where Wi-Fi compromise would materially affect operations.
  • If updates are unavailable, consult the device or distribution vendor for supported mitigations.

Validation and detection

  • Confirm each device’s kernel version, distribution backports, Wi-Fi chipset, and active driver.
  • Verify the applicable stable fix is present using vendor advisories or kernel patch records.
  • Test updated Wi-Fi functionality and stability in staging before production rollout.
  • Monitor kernel and device logs for crashes or abnormal WILC1000 driver behavior.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-39952 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-39952Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc5c77ba18ea66aa05441c71e38473efb787705a4, c5c77ba18ea66aa05441c71e38473efb787705a4, c5c77ba18ea66aa05441c71e38473efb787705a4, c5c77ba18ea66aa05441c71e38473efb787705a4unaffected
LinuxLinux4.2, 0, 6.6.108, 6.12.49, 6.16.9, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.