CVE-2026-90031: usb-storage: ene_ub6250: fix race between scan work and probe
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74, 445fc368c6bc73eff0aeb3818cf5f355facfbb16, 5082546702c32a2700894d2c0ace784e038ef6a3; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74, 445fc368c6bc73eff0aeb3818cf5f355facfbb16, 5082546702c32a2700894d2c0ace784e038ef6a3; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.39affected
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 9cd335f4f41e84d1ab88d80150ffee8dee9650d7affected · git
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 8936d95dd04d34db96d4d1e3899eee52605bbedcaffected · git
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 9c261a83131e241d67cb73ab578d0265bc19cfb5affected · git
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 9481bc04a8c351ed883a7f0e10939bbe9120ead7affected · git
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 5082546702c32a2700894d2c0ace784e038ef6a3affected · git
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74affected · git
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 996c319b8bd5ada1f62daae0d331d0b23e0f2117affected · git
- 41e568d14ec0aca1b2bb19563517aad3b06d6805 and later · before 445fc368c6bc73eff0aeb3818cf5f355facfbb16affected · git
- before 2.6.39not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90029Sep 16, 2026 · usb: storage: realtek_cr: fix use-after-free on disconnect0Monitor
- ← EarlierCVE-2026-90030Sep 16, 2026 · usb: dwc3: clear forceRM when issuing EndTransfer31Monitor
- Later →CVE-2026-90032Sep 16, 2026 · media: usbtv: keep device alive while ALSA card exists31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74 | Vendor (CNA) |
| Linux Linux | 445fc368c6bc73eff0aeb3818cf5f355facfbb16 | Vendor (CNA) |
| Linux Linux | 5082546702c32a2700894d2c0ace784e038ef6a3 | Vendor (CNA) |
| Linux Linux | 8936d95dd04d34db96d4d1e3899eee52605bbedc | Vendor (CNA) |
| Linux Linux | 9481bc04a8c351ed883a7f0e10939bbe9120ead7 | Vendor (CNA) |
| Linux Linux | 996c319b8bd5ada1f62daae0d331d0b23e0f2117 | Vendor (CNA) |
| Linux Linux | 9c261a83131e241d67cb73ab578d0265bc19cfb5 | Vendor (CNA) |
| Linux Linux | 9cd335f4f41e84d1ab88d80150ffee8dee9650d7 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/445fc368c6bc73eff0aeb3818cf5f355facfbb16
- git.kernel.org/stable/c/5082546702c32a2700894d2c0ace784e038ef6a3
- git.kernel.org/stable/c/8936d95dd04d34db96d4d1e3899eee52605bbedc
- git.kernel.org/stable/c/9481bc04a8c351ed883a7f0e10939bbe9120ead7
- git.kernel.org/stable/c/996c319b8bd5ada1f62daae0d331d0b23e0f2117
- git.kernel.org/stable/c/9c261a83131e241d67cb73ab578d0265bc19cfb5
- git.kernel.org/stable/c/9cd335f4f41e84d1ab88d80150ffee8dee9650d7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.