# CVE-2026-64464: xhci: sideband: fix ring sg table pages leak

> A memory leak in the Linux kernel xhci sideband driver allows local attackers to exhaust system memory, causing denial of service.

- **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:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64464, DEBIAN-CVE-2026-64464, GHSA-w244-36cw-6gvr, ROOT-OS-UBUNTU-2204-CVE-2026-64464, UBUNTU-CVE-2026-64464

## What is CVE-2026-64464?

CVE-2026-64464 is a memory corruption vulnerability in Linux, published on 25 Jul 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:

xhci: sideband: fix ring sg table pages leak

xhci_ring_to_sgtable() allocates a temporary pages array and
uses it to build the returned sg_table with
sg_alloc_table_from_pages().

The error paths free the pages array, but the success path
returns the sg_table without freeing it. This leaks the temporary
array every time a sideband client gets an endpoint or event ring
buffer.

Free the pages array after sg_alloc_table_from_pages() succeeds.
The returned sg_table has its own scatterlist entries and does not
depend on the temporary array after construction.

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


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

Apply the vendor's patch.

## Is CVE-2026-64464 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64464 is a memory corruption vulnerability in Linux, published on 25 Jul 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-64464 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-64464/ (Markdown: https://insights.sbomify.com/CVE-2026-64464/index.md)
```

## Sources

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

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