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-98763usb: core: clear both ep_in and ep_out for non-ep0 control endpoints

Description

In the Linux kernel, the following vulnerability has been resolved: usb: core: clear both ep_in and ep_out for non-ep0 control endpoints In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer. However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint. Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly. Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 59d2c9d70fa42e2290ff68e6430d38a1c817fcb7
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a7928ad4bbb330dfb0f726166384f319d66eb5d1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b521fe45e06b3f7042e6d1f9566ddb6f179dcb1d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 198d74dcfa129523125f46a89479d3b446b17dbe
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7a9f61476b0e8002092a52ee8295edeeb0a28d1e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1da16c46b8d7101b74bc2d72a04e23cf5c7ddea1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c50413ecb662ea43c7f487632c8114721743a277
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0e8baa78d872f2db440d8b9ded946ab8dceb89eb
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .