# CVE-2026-64601: ALSA: us144mkii: capture_urb_complete: redundant usb_anchor_urb corrupts anchor list on each resubmission

> A use-after-free vulnerability in the Linux kernel ALSA us144mkii driver allows attackers to cause denial of service or execute code via corrupted USB anchor lists.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64601, DEBIAN-CVE-2026-64601, GHSA-2x99-3h9h-f4c9, UBUNTU-CVE-2026-64601

## What is CVE-2026-64601?

CVE-2026-64601 is a high-severity use after free vulnerability in Linux, published on 6 Aug 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:

ALSA: us144mkii: capture_urb_complete: redundant usb_anchor_urb corrupts anchor list on each resubmission

In capture_urb_complete(), usb_anchor_urb() is called on every
completion callback, but the URB is already anchored from the
initial submission in tascam_trigger_start(). Each redundant call
corrupts the anchor's doubly-linked list and inflates the URB
refcount. When usb_kill_anchored_urbs() traverses the list during
stream stop / suspend / disconnect, the corrupted list leads to
use-after-free.

Remove the redundant usb_anchor_urb() from the resubmit path.

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


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

Apply the vendor's patch.

## Is CVE-2026-64601 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64601 is a high-severity use after free vulnerability in Linux, published on 6 Aug 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-64601 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-64601/ (Markdown: https://insights.sbomify.com/CVE-2026-64601/index.md)
```

## Sources

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

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