CVE-2026-68196

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.3 · Élevée
EPSS 0.4%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <4.2, 6.12.101, 0, <584c8954ad55f8b09b475be6db710fe40ceb988c, <4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de, <=7.1.*, <8ccdf8c8de87a9580df37c3c1ec53ba88cedef65, 5.15.216, <e511e93abd6eeedcd5b3c55516241f414fbde64a, <d79b92417f33424ff23dad76716ed8f2cefb1083, <=5.10.*, <4d410320e8ae5933e651660c9fadc1d380309e23, <=6.6.*, <8d50acf5420de0c4da99c2d634731c9d3164a755, 6.18.42, 7.1.6, 6.1.183, <=6.18.*, 4.2, c5c77ba18ea66aa05441c71e38473efb787705a4, <=*, <=5.15.*, <b81d0ea9e1daa215b3da68c1f4f6fb07940c2f6a, 5.10.265, 6.6.148, 7.2

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.

Gravité et risque d'exploitation

CVE-2026-68196 obtient un score CVSS de 8.3/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.41 %, ce qui la place devant 34.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <4.2, 6.12.101, 0, <584c8954ad55f8b09b475be6db710fe40ceb988c, <4c4c97b60a5e978121d9ee8cb0ab3916e5d6a8de, <=7.1.*, <8ccdf8c8de87a9580df37c3c1ec53ba88cedef65, 5.15.216, <e511e93abd6eeedcd5b3c55516241f414fbde64a, <d79b92417f33424ff23dad76716ed8f2cefb1083, <=5.10.*, <4d410320e8ae5933e651660c9fadc1d380309e23, <=6.6.*, <8d50acf5420de0c4da99c2d634731c9d3164a755, 6.18.42, 7.1.6, 6.1.183, <=6.18.*, 4.2, c5c77ba18ea66aa05441c71e38473efb787705a4, <=*, <=5.15.*, <b81d0ea9e1daa215b3da68c1f4f6fb07940c2f6a, 5.10.265, 6.6.148, 7.2) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références