CVE-2026-90031 — usb-storage: ene_ub6250: fix race between scan work and probe
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 9cd335f4f41e84d1ab88d80150ffee8dee9650d7≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 8936d95dd04d34db96d4d1e3899eee52605bbedc≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 9c261a83131e241d67cb73ab578d0265bc19cfb5≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 9481bc04a8c351ed883a7f0e10939bbe9120ead7≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 5082546702c32a2700894d2c0ace784e038ef6a3≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 996c319b8bd5ada1f62daae0d331d0b23e0f2117≥ 41e568d14ec0aca1b2bb19563517aad3b06d6805 and < 445fc368c6bc73eff0aeb3818cf5f355facfbb16 and 1 moreversion 2.6.39 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 19, 2026 · 4 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74
- git.kernel.org/stable/c/8936d95dd04d34db96d4d1e3899eee52605bbedc
- nvd.nist.gov/vuln/detail/CVE-2026-90031
- git.kernel.org/stable/c/445fc368c6bc73eff0aeb3818cf5f355facfbb16
- git.kernel.org/stable/c/5082546702c32a2700894d2c0ace784e038ef6a3
- git.kernel.org/stable/c/9cd335f4f41e84d1ab88d80150ffee8dee9650d7
- git.kernel.org/stable/c/9c261a83131e241d67cb73ab578d0265bc19cfb5
- git.kernel.org/stable/c/9481bc04a8c351ed883a7f0e10939bbe9120ead7
- github.com/advisories/GHSA-5fv5-xjmm-vvx9
- git.kernel.org/stable/c/996c319b8bd5ada1f62daae0d331d0b23e0f2117
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 1d
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 1d
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90031 is "usb-storage: ene_ub6250: fix race between scan work and probe", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.