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

> A use-after-free vulnerability in the Linux kernel USB core allows local attackers to execute arbitrary code or escalate privileges via crafted USB devices.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109347, BELL-CVE-2026-98763, DEBIAN-CVE-2026-98763, GHSA-f752-7j6x-76w7, UBUNTU-CVE-2026-98763

## What is CVE-2026-98763?

CVE-2026-98763 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98763?


## How do I fix CVE-2026-98763?

Apply the vendor's patch.

## Is CVE-2026-98763 being exploited?

There is no known exploitation of CVE-2026-98763 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98763 and fix it if it is affected.

What it is: CVE-2026-98763 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98763 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98763/ (Markdown: https://insights.sbomify.com/CVE-2026-98763/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98763
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98763
- OSV: https://osv.dev/vulnerability/CVE-2026-98763

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98763/
Summaries are generated and may contain mistakes; the official description above is the record.