Heimdall Security Logo

CVE-2026-98349

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

CVSS 7.1 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <5ce5721e8cbe3e80db8f43851cc2a2a92485ef4b, <2.6.14, 0, b453872c35cfcbdbf5a794737817f7d4e7b1b579, 6.12.112, 5.10.271, <cee6f141b3bebe62eb0363fd147acb52023935f0, 6.6.158, <=5.10.*, <=6.6.*, <14ae269c1306053ddf1ccf37c4bd66e085a652d1, 2.6.14, 6.1.189, <2c87bbc00dc93149d1dc4f803ad92d92e4ef3758, 7.2.8, <=6.18.*, 5.15.222, <=7.2.*, <23afeb5d2bdfd34c8a0a661876291a4fa9978293, <=*, <=5.15.*, <19959fb60228f6dccc40d55507f8b1a751c2dc89, <89959ff00a978f3172726d3d5f861ee6f1aae26d, 6.18.54, <ff756e6647722b7d225d882f7bdb186d8eee318e, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: libipw: reject too-short beacon and probe responses libipw_process_probe_response() and the libipw_network_init() call it makes assume the frame contains the full 36-byte beacon and probe response prefix, but the ipw2100 and ipw2200 receive paths only establish that a management frame carries the generic 24-byte three-address header. libipw_network_init() then computes the information element length as stats->len - sizeof(*beacon) stats->len is a u16 and sizeof() has type size_t, so the subtraction is evaluated as size_t and wraps instead of going negative. Truncating that to the u16 length parameter of libipw_parse_info_param() yields 65524 for a 24-byte beacon, and the parser then walks the receive buffer as if it held almost 64 KiB of information elements, reading past the allocation. Reject the frame before any fixed field is touched. Found by an AI-assisted review of length arithmetic in management frame parsers. Verified with a KUnit case under Generic KASAN on arm64 under QEMU; I do not have the hardware, so it is not tested on a real device.

Gravité et risque d'exploitation

CVE-2026-98349 obtient un score CVSS de 7.1/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.26 %, ce qui la place devant 16.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <5ce5721e8cbe3e80db8f43851cc2a2a92485ef4b, <2.6.14, 0, b453872c35cfcbdbf5a794737817f7d4e7b1b579, 6.12.112, 5.10.271, <cee6f141b3bebe62eb0363fd147acb52023935f0, 6.6.158, <=5.10.*, <=6.6.*, <14ae269c1306053ddf1ccf37c4bd66e085a652d1, 2.6.14, 6.1.189, <2c87bbc00dc93149d1dc4f803ad92d92e4ef3758, 7.2.8, <=6.18.*, 5.15.222, <=7.2.*, <23afeb5d2bdfd34c8a0a661876291a4fa9978293, <=*, <=5.15.*, <19959fb60228f6dccc40d55507f8b1a751c2dc89, <89959ff00a978f3172726d3d5f861ee6f1aae26d, 6.18.54, <ff756e6647722b7d225d882f7bdb186d8eee318e, 7.3) 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

Rechercher une autre CVE