Answer in brief
CVE-2026-68196 records a High severity (CVSS 8.3) vulnerability in wifi: wilc1000: validate assoc response length before subtracting header. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c5c77ba18ea66aa05441c71e38473efb787705a4 <584c8954ad55f8b09b475be6db710fe40ceb988c || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <4d410320e8ae5933e651660c9fadc1d380309e23 || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <e511e93abd6eeedcd5b3c55516241f414fbde64a || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <8ccdf8c8de87a9580df37c3c1ec53ba88cedef65 || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de | 584c8954ad55f8b09b475be6db710fe40ceb988c, 4d410320e8ae5933e651660c9fadc1d380309e23, e511e93abd6eeedcd5b3c55516241f414fbde64a, 8ccdf8c8de87a9580df37c3c1ec53ba88cedef65, 4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de |
| Linux/Linuxgeneric | 4.2 | Not reported |
| Linux/Linuxgeneric | >=c5c77ba18ea66aa05441c71e38473efb787705a4 <d79b92417f33424ff23dad76716ed8f2cefb1083 || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <b81d0ea9e1daa215b3da68c1f4f6fb07940c2f6a || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <8d50acf5420de0c4da99c2d634731c9d3164a755 || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <584c8954ad55f8b09b475be6db710fe40ceb988c || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <4d410320e8ae5933e651660c9fadc1d380309e23 || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <e511e93abd6eeedcd5b3c55516241f414fbde64a || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <8ccdf8c8de87a9580df37c3c1ec53ba88cedef65 || >=c5c77ba18ea66aa05441c71e38473efb787705a4 <4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de | d79b92417f33424ff23dad76716ed8f2cefb1083, b81d0ea9e1daa215b3da68c1f4f6fb07940c2f6a, 8d50acf5420de0c4da99c2d634731c9d3164a755, 584c8954ad55f8b09b475be6db710fe40ceb988c, 4d410320e8ae5933e651660c9fadc1d380309e23, e511e93abd6eeedcd5b3c55516241f414fbde64a, 8ccdf8c8de87a9580df37c3c1ec53ba88cedef65, 4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.