Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98763: usb: core: clear both ep_in and ep_out for non-ep0 control endpoints

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Fixed version: Linux Linux 0e8baa78d872f2db440d8b9ded946ab8dceb89eb, 198d74dcfa129523125f46a89479d3b446b17dbe, 1da16c46b8d7101b74bc2d72a04e23cf5c7ddea1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.

Low priority for now. Upgrade to Linux Linux 0e8baa78d872f2db440d8b9ded946ab8dceb89eb, 198d74dcfa129523125f46a89479d3b446b17dbe, 1da16c46b8d7101b74bc2d72a04e23cf5c7ddea1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 18, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98763

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 59d2c9d70fa42e2290ff68e6430d38a1c817fcb7affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a7928ad4bbb330dfb0f726166384f319d66eb5d1affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b521fe45e06b3f7042e6d1f9566ddb6f179dcb1daffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 198d74dcfa129523125f46a89479d3b446b17dbeaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7a9f61476b0e8002092a52ee8295edeeb0a28d1eaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1da16c46b8d7101b74bc2d72a04e23cf5c7ddea1affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c50413ecb662ea43c7f487632c8114721743a277affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0e8baa78d872f2db440d8b9ded946ab8dceb89ebaffected · git
    • before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.10-17.2.10-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98761Oct 18, 2026 · usb: typec: tcpm: recover after failure to start the frs ams
    0Monitor
  • ← EarlierCVE-2026-98762Oct 18, 2026 · USB: dwc2: shut down wakeup timer before freeing HCD state
    0Monitor
  • Later →CVE-2026-98764Oct 18, 2026 · usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0e8baa78d872f2db440d8b9ded946ab8dceb89ebVendor (CNA)
Linux Linux198d74dcfa129523125f46a89479d3b446b17dbeVendor (CNA)
Linux Linux1da16c46b8d7101b74bc2d72a04e23cf5c7ddea1Vendor (CNA)
Linux Linux59d2c9d70fa42e2290ff68e6430d38a1c817fcb7Vendor (CNA)
Linux Linux7a9f61476b0e8002092a52ee8295edeeb0a28d1eVendor (CNA)
Linux Linuxa7928ad4bbb330dfb0f726166384f319d66eb5d1Vendor (CNA)
Linux Linuxb521fe45e06b3f7042e6d1f9566ddb6f179dcb1dVendor (CNA)
Linux Linuxc50413ecb662ea43c7f487632c8114721743a277Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.06.6.161.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 7, 2026+20 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records