CVE-2026-68196

wifi: wilc1000: validate assoc response length before subtracting header

HIGH
8.3
CVSS Score
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.3
Exploit prediction
EPSS 0.4%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: validate assoc response length before subtracting header wilc_parse_assoc_resp_info() computes the trailing IE length as ies_len = buffer_len - sizeof(*res); without first checking that buffer_len is at least sizeof(struct wilc_assoc_resp) (6 bytes). buffer_len is the length reported for a received association response (host_int_parse_assoc_resp_info() passes hif_drv->assoc_resp / assoc_resp_info_len straight in) and must be validated before the driver accesses the fixed header. For a frame shorter than the 6-byte fixed header, the subtraction wraps. For a four-byte response the result is truncated to a u16 ies_len of 65534, so kmemdup() then attempts to copy 65534 bytes starting at buffer + sizeof(*res), beyond the valid association-response data (CWE-125). A response shorter than four bytes can also cause an out-of-bounds read of res->status_code at offsets 2 and 3. Reject frames too short to hold the fixed header before touching the header or computing ies_len. Also set the connection status to a failure on this path: the caller falls through to a "conn_info->status == WLAN_STATUS_SUCCESS" check after the parser returns, so leaving the status untouched could let a malformed short response be treated as a successful association.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.2 ≤ v < 5.10.2654.2 ≤ v < 5.15.2164.2 ≤ v < 6.1.1834.2 ≤ v < 6.12.1014.2 ≤ v < 6.18.424.2 ≤ v < 6.6.1484.2 ≤ v < 7.1.64.2 ≤ v < 7.24.2c5c77ba18ea66aa05441c71e38473efb787705a4
Vendor states this is fixed in 4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de (fixed)
Vendor states this is fixed in 4d410320e8ae5933e651660c9fadc1d380309e23 (fixed)
Vendor states this is fixed in 584c8954ad55f8b09b475be6db710fe40ceb988c (fixed)
Vendor states this is fixed in 8ccdf8c8de87a9580df37c3c1ec53ba88cedef65 (fixed)
Vendor states this is fixed in 8d50acf5420de0c4da99c2d634731c9d3164a755 (fixed)
Vendor states this is fixed in b81d0ea9e1daa215b3da68c1f4f6fb07940c2f6a (fixed)
Vendor states this is fixed in d79b92417f33424ff23dad76716ed8f2cefb1083 (fixed)
Vendor states this is fixed in e511e93abd6eeedcd5b3c55516241f414fbde64a (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

8.3HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card