# CVE-2026-98428: ALSA: usb: 6fire: Avoid embedded URBs

> A use-after-free vulnerability in the Linux kernel USB 6fire driver allows local attackers to execute arbitrary code or escalate privileges via physical USB access.

- **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:** 14 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-108123, BELL-CVE-2026-98428, DEBIAN-CVE-2026-98428, GHSA-xcw2-5vfj-h3fm, UBUNTU-CVE-2026-98428

## What is CVE-2026-98428?

CVE-2026-98428 is an use after free vulnerability in Linux, published on 14 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:

ALSA: usb: 6fire: Avoid embedded URBs

The USB 6fire driver uses URBs embedded in different structs for PCM,
MIDI and communication, and this is basically a buggy implementation
nowadays; since a URB is managed with a refcount, this may lead to a
UAF when the URB is released asynchronously.

For addressing the problem, this patch converts those embedded URBs to
ones that are properly allocated via usb_alloc_urb().  The
pcm_urb.packets[] is gone, as it's allocated by usb_alloc_urb(), hence
it's found in urb.iso_frame_desc[] instead.

The conversions are rather straightforward; each embedded struct urb
is changed to a pointer, and its callers are updated accordingly.
The resource for those structs are released in the common destructor
functions (usb6fire_comm_free(), etc), which are called at both the
init error path and the disconnect.

No functional changes, only compile-tested.

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


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

Apply the vendor's patch.

## Is CVE-2026-98428 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98428 is an use after free vulnerability in Linux, published on 14 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-98428 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-98428/ (Markdown: https://insights.sbomify.com/CVE-2026-98428/index.md)
```

## Sources

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

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