# CVE-2026-97539: usb: xusbatm: don't rely on id table pointer arithmetic

> A memory corruption vulnerability in the Linux kernel xusbatm USB driver allows attackers with physical access to cause crashes or execute code via dynamic ID handling.

- **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 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104385, BELL-CVE-2026-97539, DEBIAN-CVE-2026-97539, GHSA-xvgf-wgq5-q9ph, UBUNTU-CVE-2026-97539

## What is CVE-2026-97539?

CVE-2026-97539 is a memory corruption vulnerability in Linux, published on 25 Sep 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: xusbatm: don't rely on id table pointer arithmetic

The current code is broken when dynamic ID is involved; in such cases
usb_device_id parameter of probe lives on the heap and the pointer
arithmetic will get an index that is wildly out of bound. xusbatm
initialize the USB device IDs dynamically so it can just use driver_info
too.

Even with conversion, xusbatm still cannot support dynamic IDs, so also set
no_dynamic_id.

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


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

Apply the vendor's patch.

## Is CVE-2026-97539 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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