CVE-2025-39952 (GCVE-0-2025-39952)
Vulnerability from cvelistv5
Published
2025-10-04 07:31
Modified
2026-08-05 12:06
Severity ?
8.8 (High) - CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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'.
References
Impacted products
Vendor Product Version
Linux Linux Version: c5c77ba18ea66aa05441c71e38473efb787705a4
Version: c5c77ba18ea66aa05441c71e38473efb787705a4
Version: c5c77ba18ea66aa05441c71e38473efb787705a4
Version: c5c77ba18ea66aa05441c71e38473efb787705a4
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "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": "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.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.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-08-05T12:06:25.699Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "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-08-05T12:06:25.699Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.