# CVE-2026-90031: usb-storage: ene_ub6250: fix race between scan work and probe

> A race condition in the Linux kernel's ene_ub6250 USB storage driver can cause a denial of service when concurrent operations access shared URB resources.

- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101451, BELL-CVE-2026-90031, DEBIAN-CVE-2026-90031, GHSA-5fv5-xjmm-vvx9, UBUNTU-CVE-2026-90031

## What is CVE-2026-90031?

CVE-2026-90031 is a vulnerability in Linux, published on 16 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-storage: ene_ub6250: fix race between scan work and probe

ene_ub6250_probe() calls usb_stor_probe2(), which starts the usb-storage
infrastructure and schedules the delayed scan work.  The driver then
calls ene_get_card_type(), which sends an ENE command through
ene_send_scsi_cmd() and the usb-storage bulk transfer helpers.

Both the delayed scan work, through usb_stor_Bulk_max_lun(), and
ene_get_card_type() use us->current_urb.  The scan work serializes this
access with us->dev_mutex, but the ENE card-type probe does not.  If the
scan work runs while ene_get_card_type() is still using us->current_urb,
usb_submit_urb() warns that the URB is already active.

Serialize ene_get_card_type() with us->dev_mutex, matching the locking
used by the scan path.

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


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

Apply the vendor's patch.

## Is CVE-2026-90031 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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