CVE-2025-68331
usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer When a UAS device is unplugged during data transfer, there is a probability of a system panic occurring. The root cause is an access to an invalid memory address during URB callback handling. Specifically, this happens when the dma_direct_unmap_sg() function is called within the usb_hcd_unmap_urb_for_dma() interface, but the sg->dma_address field is 0 and the sg data structure has already been freed. The SCSI driver sends transfer commands by invoking uas_queuecommand_lck() in uas.c, using the uas_submit_urbs() function to submit requests to USB. Within the uas_submit_urbs() implementation, three URBs (sense_urb, data_urb, and cmd_urb) are sequentially submitted. Device removal may occur at any point during uas_submit_urbs execution, which may result in URB submission failure. However, some URBs might have been successfully submitted before the failure, and uas_submit_urbs will return the -ENODEV error code in this case. The current error handling directly calls scsi_done(). In the SCSI driver, this eventually triggers scsi_complete() to invoke scsi_end_request() for releasing the sgtable. The successfully submitted URBs, when being unlinked to giveback, call usb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg unmapping operations since the sg data structure has already been freed. This patch modifies the error condition check in the uas_submit_urbs() function. When a UAS device is removed but one or more URBs have already been successfully submitted to USB, it avoids immediately invoking scsi_done() and save the cmnd to devinfo->cmnd array. If the successfully submitted URBs is completed before devinfo->resetting being set, then the scsi_done() function will be called within uas_try_complete() after all pending URB operations are finalized. Otherwise, the scsi_done() function will be called within uas_zap_pending(), which is executed after usb_kill_anchored_urbs(). The error handling only takes effect when uas_queuecommand_lck() calls uas_submit_urbs() and returns the error value -ENODEV . In this case, the device is disconnected, and the flow proceeds to uas_disconnect(), where uas_zap_pending() is invoked to call uas_try_complete().
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 5 months later
· 5 months 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: Deferred.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (10 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected eb2a86ae8c544be0ab04aa8169390c0669bc7148 – < 6289fc489e94c9beb6be2b502ccc263663733d72
- affected eb2a86ae8c544be0ab04aa8169390c0669bc7148 – < 66ac05e7b0d6bbd1bee9fcf729e20fd4cce86d17
- affected eb2a86ae8c544be0ab04aa8169390c0669bc7148 – < 75f8e2643085db4f7e136fc6b368eb114dd80a64
- affected eb2a86ae8c544be0ab04aa8169390c0669bc7148 – < e3a55221f4de080cb7a91ba10f01c4f708603f8d
- affected eb2a86ae8c544be0ab04aa8169390c0669bc7148 – < 2b90a8131c83f6f2be69397d2b7d14d217d95d2f
- affected eb2a86ae8c544be0ab04aa8169390c0669bc7148 – < 426edbfc88b22601ea34a441a469092e7b301c52
- affected eb2a86ae8c544be0ab04aa8169390c0669bc7148 – < 26d56a9fcb2014b99e654127960aa0a48a391e3c
- affected 5.10
- unaffected < 5.10
- unaffected 5.10.247 – ≤ 5.10.*
- unaffected 5.15.197 – ≤ 5.15.*
- unaffected 6.1.159 – ≤ 6.1.*
- unaffected 6.6.119 – ≤ 6.6.*
- unaffected 6.12.61 – ≤ 6.12.*
- unaffected 6.17.11 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
7
- https://git.kernel.org/stable/c/6289fc489e94c9beb6be2b502ccc263663733d72 (opens in a new tab)
- https://git.kernel.org/stable/c/66ac05e7b0d6bbd1bee9fcf729e20fd4cce86d17 (opens in a new tab)
- https://git.kernel.org/stable/c/75f8e2643085db4f7e136fc6b368eb114dd80a64 (opens in a new tab)
- https://git.kernel.org/stable/c/e3a55221f4de080cb7a91ba10f01c4f708603f8d (opens in a new tab)
- https://git.kernel.org/stable/c/2b90a8131c83f6f2be69397d2b7d14d217d95d2f (opens in a new tab)
- https://git.kernel.org/stable/c/426edbfc88b22601ea34a441a469092e7b301c52 (opens in a new tab)
- https://git.kernel.org/stable/c/26d56a9fcb2014b99e654127960aa0a48a391e3c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-204726 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68331)Record last updated .