CVE-2026-98764

usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC

State
Published
Severity
Not scored
Published
Oct 18, 2026
Updated
Oct 30, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • c559a353410939c0884e83bdb0e2420a986ac53b to before c5f452e057df6ef89300523d13ad6833bfd199cdAffected
  • c559a353410939c0884e83bdb0e2420a986ac53b to before e5b9d6bb2a8906a1188c9a90cc8d102de3f07cadAffected
  • c559a353410939c0884e83bdb0e2420a986ac53b to before 7ef0ad5f462fa95bc4c6647d097d7c0384245b9cAffected
  • c559a353410939c0884e83bdb0e2420a986ac53b to before 06ac8609d6d185ac18c1d6a6a8a9b99e398bd124Affected
  • c559a353410939c0884e83bdb0e2420a986ac53b to before 9d8761b3c133f6c6a6d3486839dac60e2cf4bfe3Affected
  • c559a353410939c0884e83bdb0e2420a986ac53b to before 7811d8e26c77f8eea79e22d0d14c67ec0658b348Affected
  • c559a353410939c0884e83bdb0e2420a986ac53b to before 35ab269602e1f7c4c0fe6ea3477264bea77eced3Affected
  • c559a353410939c0884e83bdb0e2420a986ac53b to before 9cd072788c76595529eb38f42bf94d23852f8534Affected
LinuxLinux
  • 3.18Affected
  • before 3.18Not affected
  • 5.10.273 through 5.10.*Not affected
  • 5.15.224 through 5.15.*Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.113 through 6.12.*Not affected
  • 6.18.56 through 6.18.*Not affected
  • 7.2.10 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.