CVE-2026-98764

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <7811d8e26c77f8eea79e22d0d14c67ec0658b348, 7.2.10, <=*, <9cd072788c76595529eb38f42bf94d23852f8534, <=6.12.*, 6.18.56, <=6.18.*, c559a353410939c0884e83bdb0e2420a986ac53b, <3.18, 0, <35ab269602e1f7c4c0fe6ea3477264bea77eced3, 7.3, <=7.2.*, 3.18, <9d8761b3c133f6c6a6d3486839dac60e2cf4bfe3, 6.12.113

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC When user space sets up FunctionFS with only full-speed descriptors (e.g., flags = FUNCTIONFS_HAS_FS_DESC) and the gadget operates at a higher speed (such as USB_SPEED_HIGH or USB_SPEED_SUPER), config_ep_by_speed() detects that the function lacks descriptors for the current speed, logs a warning, and falls back to full-speed descriptors. The endpoint is then successfully enabled via usb_ep_enable(), and epfile->ep becomes valid. However, when user space subsequently issues the FUNCTIONFS_ENDPOINT_DESC ioctl to query the endpoint descriptor, ffs_epfile_ioctl() selects the descriptor index solely based on gadget->speed: switch (epfile->ffs->gadget->speed) { case USB_SPEED_SUPER: case USB_SPEED_SUPER_PLUS: desc_idx = 2; break; case USB_SPEED_HIGH: desc_idx = 1; break; default: desc_idx = 0; } desc = epfile->ep->descs[desc_idx]; memcpy(&desc1, desc, desc->bLength); Because user space only supplied full-speed descriptors, epfile->ep->descs[1] is NULL. Dereferencing desc->bLength triggers an immediate kernel NULL pointer dereference panic. Fix this by falling back through lower speed descriptors if the current speed descriptor was not supplied, matching the fallback logic in config_ep_by_speed() and historical f_fs behavior. If still missing, fall back to epfile->ep->ep->desc (the active descriptor), and return -EINVAL safely if no valid descriptor is found. In addition, mark desc as const to match struct usb_ep::desc and avoid discarding qualifiers.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <7811d8e26c77f8eea79e22d0d14c67ec0658b348, 7.2.10, <=*, <9cd072788c76595529eb38f42bf94d23852f8534, <=6.12.*, 6.18.56, <=6.18.*, c559a353410939c0884e83bdb0e2420a986ac53b, <3.18, 0, <35ab269602e1f7c4c0fe6ea3477264bea77eced3, 7.3, <=7.2.*, 3.18, <9d8761b3c133f6c6a6d3486839dac60e2cf4bfe3, 6.12.113) 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