CVE-2025-39952 (GCVE-0-2025-39952)

Vulnerability from cvelistv5 – Published: 2025-10-04 07:31 – Updated: 2026-10-30 12:22
VLAI
Title
wifi: wilc1000: avoid buffer overflow in WID string configuration
Summary
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'.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: c5c77ba18ea66aa05441c71e38473efb787705a4 , < 5f1578a8684794318a60a022cedbffaa3dc444ce (git)
Affected: c5c77ba18ea66aa05441c71e38473efb787705a4 , < 6085291a1a5865d4ad70f0e5812d524ebd5d1711 (git)
Affected: c5c77ba18ea66aa05441c71e38473efb787705a4 , < 2203ef417044b10a8563ade6a17c74183745d72e (git)
Affected: c5c77ba18ea66aa05441c71e38473efb787705a4 , < ae50f8562306a7ea1cf3c9722f97ee244f974729 (git)
Affected: c5c77ba18ea66aa05441c71e38473efb787705a4 , < fe9e4d0c39311d0f97b024147a0d155333f388b5 (git)
Create a notification for this product.
Linux Linux Affected: 4.2
Unaffected: 0 , < 4.2 (semver)
Unaffected: 6.1.191 , ≤ 6.1.* (semver)
Unaffected: 6.6.108 , ≤ 6.6.* (semver)
Unaffected: 6.12.49 , ≤ 6.12.* (semver)
Unaffected: 6.16.9 , ≤ 6.16.* (semver)
Unaffected: 6.17 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/wireless/microchip/wilc1000/wlan_cfg.c",
            "drivers/net/wireless/microchip/wilc1000/wlan_cfg.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5f1578a8684794318a60a022cedbffaa3dc444ce",
              "status": "affected",
              "version": "c5c77ba18ea66aa05441c71e38473efb787705a4",
              "versionType": "git"
            },
            {
              "lessThan": "6085291a1a5865d4ad70f0e5812d524ebd5d1711",
              "status": "affected",
              "version": "c5c77ba18ea66aa05441c71e38473efb787705a4",
              "versionType": "git"
            },
            {
              "lessThan": "2203ef417044b10a8563ade6a17c74183745d72e",
              "status": "affected",
              "version": "c5c77ba18ea66aa05441c71e38473efb787705a4",
              "versionType": "git"
            },
            {
              "lessThan": "ae50f8562306a7ea1cf3c9722f97ee244f974729",
              "status": "affected",
              "version": "c5c77ba18ea66aa05441c71e38473efb787705a4",
              "versionType": "git"
            },
            {
              "lessThan": "fe9e4d0c39311d0f97b024147a0d155333f388b5",
              "status": "affected",
              "version": "c5c77ba18ea66aa05441c71e38473efb787705a4",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/wireless/microchip/wilc1000/wlan_cfg.c",
            "drivers/net/wireless/microchip/wilc1000/wlan_cfg.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.2"
            },
            {
              "lessThan": "4.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.191",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.108",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.49",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.16.*",
              "status": "unaffected",
              "version": "6.16.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.17",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.191",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.108",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.49",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.16.9",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.17",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wilc1000: avoid buffer overflow in WID string configuration\n\nFix the following copy overflow warning identified by Smatch checker.\n\n drivers/net/wireless/microchip/wilc1000/wlan_cfg.c:184 wilc_wlan_parse_response_frame()\n        error: \u0027__memcpy()\u0027 \u0027cfg-\u003es[i]-\u003estr\u0027 copy overflow (512 vs 65537)\n\nThis patch introduces size check before accessing the memory buffer.\nThe checks are base on the WID type of received data from the firmware.\nFor WID string configuration, the size limit is determined by individual\nelement size in \u0027struct wilc_cfg_str_vals\u0027 that is maintained in \u0027len\u0027 field\nof \u0027struct wilc_cfg_str\u0027."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:A - The overflow length and payload originate from the association-response management frame supplied over the air by the AP and relayed by the WILC firmware as a WID_ASSOC_RES_INFO config reply, so an attacker must be within WiFi radio range of the target (rogue/evil-twin AP or management-frame injection). Per kernel guidance, WiFi-frame-sourced bugs are Adjacent.\nAC:L - The attacker fully controls the 16-bit length field and the payload of the association response and can force association attempts repeatedly, so the overflow triggers deterministically on every connect with no race or uncontrollable precondition.\nPR:N - Association responses are unprotected frames exchanged before any WPA/802.1X credential verification, so the attacker needs no credentials on the target network and no account or privileges on the victim device.\nUI:N - A device with a saved profile auto-associates to a spoofed SSID, and an in-range attacker can inject a spoofed association response during an ordinary connection to a legitimate network, so no victim action is required.\nS:U - The corruption is confined to the kernel heap of the same system running the driver; no VM, IOMMU, or other security-authority boundary is crossed.\nC:H - The unbounded copy reads far past the received packet inside the 96 KB RX buffer into assoc_rsp, which is then exposed to userspace as association-response IEs via wilc_wlan_cfg_get_val(), and the resulting heap corruption provides further arbitrary-read primitives.\nI:H - Up to 65537 bytes of fully attacker-controlled data are written past a ~648-byte kzalloc\u0027d object, an out-of-bounds write that corrupts adjacent slab objects and is a standard primitive for control-flow hijack and privilege escalation.\nA:H - A multi-kilobyte heap overflow reliably corrupts slab metadata and neighbouring allocations, producing kernel panics or oopses on the affected embedded/IoT device."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-30T12:22:39.571Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/5f1578a8684794318a60a022cedbffaa3dc444ce"
        },
        {
          "url": "https://git.kernel.org/stable/c/6085291a1a5865d4ad70f0e5812d524ebd5d1711"
        },
        {
          "url": "https://git.kernel.org/stable/c/2203ef417044b10a8563ade6a17c74183745d72e"
        },
        {
          "url": "https://git.kernel.org/stable/c/ae50f8562306a7ea1cf3c9722f97ee244f974729"
        },
        {
          "url": "https://git.kernel.org/stable/c/fe9e4d0c39311d0f97b024147a0d155333f388b5"
        }
      ],
      "title": "wifi: wilc1000: avoid buffer overflow in WID string configuration",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-39952",
    "datePublished": "2025-10-04T07:31:12.445Z",
    "dateReserved": "2025-04-16T07:20:57.148Z",
    "dateUpdated": "2026-10-30T12:22:39.571Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-39952",
      "date": "2026-11-19",
      "epss": "0.00294",
      "percentile": "0.22385"
    },
    "microsoft_vex": {
      "current_release_date": "2025-10-05T01:02:53.000Z",
      "cve": "CVE-2025-39952",
      "id": "msrc_CVE-2025-39952",
      "initial_release_date": "2025-10-05T01:02:53.000Z",
      "product_status:known_not_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "wifi: wilc1000: avoid buffer overflow in WID string configuration",
      "url": "https://msrc.microsoft.com/csaf/vex/2025/msrc_cve-2025-39952.json",
      "version": "1"
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-09T18:32:39+00:00",
      "cve": "CVE-2025-39952",
      "id": "CVE-2025-39952",
      "initial_release_date": "2025-10-04T00:00:00+00:00",
      "product_status:known_not_affected": "200",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: wifi: wilc1000: avoid buffer overflow in WID string configuration",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-39952.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.