CVE-2026-68196

HIGHPre-NVD 8.38.3
EchelonGraph scoreHIGH confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.3
EG Score
8.3(high)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

wifi: wilc1000: validate assoc response length before subtracting header - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e511e93abd6eeedcd5b3c55516241f414fbde64a
generic

wifi: wilc1000: validate assoc response length before subtracting header - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ccdf8c8de87a9580df37c3c1ec53ba88cedef65
generic

wifi: wilc1000: validate assoc response length before subtracting header - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/584c8954ad55f8b09b475be6db710fe40ceb988c
generic

wifi: wilc1000: validate assoc response length before subtracting header - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d410320e8ae5933e651660c9fadc1d380309e23
generic

wifi: wilc1000: validate assoc response length before subtracting header - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de

Vendor Advisories for CVE-2026-68196(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 36× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 06:08 UTCEG score recompute
  2. 2026-08-21 06:08 UTCVendor advisory
  3. 2026-08-21 06:08 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 17:54 UTCGHSA enrichment
  6. 2026-08-20 05:40 UTCGHSA enrichment
  7. 2026-08-19 17:25 UTCEG score recompute
  8. 2026-08-19 17:25 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 16:55 UTCEG score recompute
  11. 2026-08-19 16:55 UTCGHSA enrichment
  12. 2026-08-19 08:06 UTCGHSA enrichment
  13. 2026-08-18 19:52 UTCEG score recompute
  14. 2026-08-18 19:52 UTCGHSA enrichment
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 07:38 UTCGHSA enrichment
  18. 2026-08-17 19:20 UTCEG score recompute
  19. 2026-08-17 19:20 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 05:38 UTCEG score recompute
  22. 2026-08-17 05:38 UTCGHSA enrichment
  23. 2026-08-17 05:09 UTCEG score recompute
  24. 2026-08-17 05:09 UTCGHSA enrichment
  25. 2026-08-17 00:54 UTCEG score recompute
Show 23 more
  1. 2026-08-17 00:54 UTCGHSA enrichment
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 12:40 UTCEG score recompute
  4. 2026-08-16 12:40 UTCGHSA enrichment
  5. 2026-08-16 00:26 UTCGHSA enrichment
  6. 2026-08-15 12:12 UTCEG score recompute
  7. 2026-08-15 12:12 UTCGHSA enrichment
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 23:58 UTCGHSA enrichment
  10. 2026-08-14 11:44 UTCEG score recompute
  11. 2026-08-14 11:44 UTCGHSA enrichment
  12. 2026-08-13 23:30 UTCEG score recompute
  13. 2026-08-13 23:30 UTCGHSA enrichment
  14. 2026-08-13 22:45 UTCEG score recompute 8.30
  15. 2026-08-13 22:45 UTCGHSA enrichment
  16. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 8.3 · severity → HIGH
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 18:43 UTCEG score recompute
  19. 2026-08-13 18:43 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-10 13:24 UTCNVD update
  22. 2026-08-10 12:20 UTCEG score recompute
  23. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68196?
CVE-2026-68196 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: validate assoc response length before subtracting header wilcparseassocrespinfo() computes the trailing IE length as ieslen = bufferlen - sizeof(*res); without first checking that buffer_len is at least…
When was CVE-2026-68196 disclosed?
CVE-2026-68196 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68196 actively exploited?
CVE-2026-68196 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.8% of all scored CVEs.
What is the CVSS score of CVE-2026-68196?
CVE-2026-68196 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-68196?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68196, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68196

Explore →

Is Your Infrastructure Affected by CVE-2026-68196?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.