Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68196wifi: wilc1000: validate assoc response length before subtracting header

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 9 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68196, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.3CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
NVDNVD · Received3.1High8.3CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
EPSS (exploitation in 30 days)
0.41% · top 64% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.3.

Affected products

  • Linux · Linux

    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < d79b92417f33424ff23dad76716ed8f2cefb1083
    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < b81d0ea9e1daa215b3da68c1f4f6fb07940c2f6a
    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < 8d50acf5420de0c4da99c2d634731c9d3164a755
    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < 584c8954ad55f8b09b475be6db710fe40ceb988c
    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < 4d410320e8ae5933e651660c9fadc1d380309e23
    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < e511e93abd6eeedcd5b3c55516241f414fbde64a
    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < 8ccdf8c8de87a9580df37c3c1ec53ba88cedef65
    • affected c5c77ba18ea66aa05441c71e38473efb787705a4 – < 4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68196 badge
[![CVE-2026-68196](https://cveledger.app/badge/CVE-2026-68196.svg)](https://cveledger.app/cve/CVE-2026-68196)

Record last updated .