Linux Kernel up to 7.3-rc1 ene_ub6250 ene_ub6250_probe race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.8$0-$5k0.00-

Summaryinfo

A vulnerability has been found in Linux Kernel up to 7.3-rc1 and classified as very critical. Affected is the function ene_ub6250_probe of the component ene_ub6250. This manipulation causes race condition. This vulnerability is tracked as CVE-2026-90031. The attack is restricted to local execution. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.3-rc1 and classified as very critical. Affected by this vulnerability is the function ene_ub6250_probe of the component ene_ub6250. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-90031 since 09/11/2026. The exploitation appears to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/16/2026).

Upgrading to version 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5 or 7.3-rc2 eliminates this vulnerability. Applying the patch 9cd335f4f41e84d1ab88d80150ffee8dee9650d7/8936d95dd04d34db96d4d1e3899eee52605bbedc/9c261a83131e241d67cb73ab578d0265bc19cfb5/9481bc04a8c351ed883a7f0e10939bbe9120ead7/5082546702c32a2700894d2c0ace784e038ef6a3/1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74/996c319b8bd5ada1f62daae0d331d0b23e0f2117/445fc368c6bc73eff0aeb3818cf5f355facfbb16 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.2
VulDB Meta Temp Score: 7.8

VulDB Base Score: 8.2
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.270/5.15.221/6.1.188/6.6.157/6.12.110/6.18.51/7.2.5/7.3-rc2
Patch: 9cd335f4f41e84d1ab88d80150ffee8dee9650d7/8936d95dd04d34db96d4d1e3899eee52605bbedc/9c261a83131e241d67cb73ab578d0265bc19cfb5/9481bc04a8c351ed883a7f0e10939bbe9120ead7/5082546702c32a2700894d2c0ace784e038ef6a3/1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74/996c319b8bd5ada1f62daae0d331d0b23e0f2117/445fc368c6bc73eff0aeb3818cf5f355facfbb16

Timelineinfo

09/11/2026 CVE reserved
09/16/2026 +5 days Advisory disclosed
09/16/2026 +0 days VulDB entry created
09/16/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-90031 (🔒)
GCVE (CVE): GCVE-0-2026-90031
GCVE (VulDB): GCVE-100-405877

Entryinfo

Created: 09/16/2026 15:31
Changes: 09/16/2026 15:31 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!