Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 9cd335f4f41e84d1ab88d80150ffee8dee9650d7
    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 8936d95dd04d34db96d4d1e3899eee52605bbedc
    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 9c261a83131e241d67cb73ab578d0265bc19cfb5
    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 9481bc04a8c351ed883a7f0e10939bbe9120ead7
    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 5082546702c32a2700894d2c0ace784e038ef6a3
    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 1c67f2ba9c5f7c5ab3670671c0d51c6504bcaf74
    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 996c319b8bd5ada1f62daae0d331d0b23e0f2117
    • affected 41e568d14ec0aca1b2bb19563517aad3b06d6805 – < 445fc368c6bc73eff0aeb3818cf5f355facfbb16
  • Linux · Linux

    • affected 2.6.39
    • unaffected < 2.6.39
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90031 badge
[![CVE-2026-90031](https://cveledger.app/badge/CVE-2026-90031.svg)](https://cveledger.app/cve/CVE-2026-90031)

Record last updated .