cve.bz

CVE-2025-68331 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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().
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.247
  • Linux Linux: fixed in 5.15.197
  • Linux Linux: fixed in 6.1.159
  • Linux Linux: fixed in 6.6.119
  • Linux Linux: fixed in 6.12.61
  • Linux Linux: fixed in 6.17.11
  • Linux Linux: fixed in 6.18
  • Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-68331 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68331?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68331?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68331 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-68331

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68331](https://cve.bz/cve/badge/CVE-2025-68331.svg)](https://cve.bz/cve/CVE-2025-68331)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68331"><img src="https://cve.bz/cve/badge/CVE-2025-68331.svg" alt="CVE-2025-68331"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.10 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.247
Linux5.155.15.197
Linux6.16.1.159
Linux6.66.6.119
Linux6.126.12.61
Linux6.176.17.11
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux-6.16.1.159-1~deb11u1DLA-4436-1
Debian12linux6.1.159-1DEBIAN-CVE-2025-68331
Debian13linux6.12.63-1DEBIAN-CVE-2025-68331
Debian14linux6.17.11-1DEBIAN-CVE-2025-68331
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68331
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68331
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68331
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-173.183UBUNTU-CVE-2025-68331 USN-8096-1
Ubuntu22.04:LTSlinux-aws5.15.0-1103.110UBUNTU-CVE-2025-68331 USN-8096-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1050.53~22.04.1UBUNTU-CVE-2025-68331 USN-8095-4
Ubuntu22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-68331 USN-8163-2
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-68331 USN-8126-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-68331
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-68331
Ubuntu22.04:LTSlinux-gcp5.15.0-1103.112UBUNTU-CVE-2025-68331 USN-8096-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-68331 USN-8095-1
74 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6kernel-default6.4.0-150600.23.84.1SUSE-SU-2026:0293-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.9.1SUSE-SU-2026:20228-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_191-150600.13.3.1SUSE-SU-2026:0293-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_81-150700.1.3.1SUSE-SU-2026:0278-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_81-150700.15.3.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.28.1.150700.17.19.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure, kernel-syms-azure, kernel-source-azure6.4.0-150700.20.24.1SUSE-SU-2026:0281-1
SUSELinux Enterprise Server 15 SP6-LTSSkernel-64kb, kernel-docs, kernel-syms and 4 more6.4.0-150600.23.84.1SUSE-SU-2026:0293-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6kernel-default-base6.4.0-150600.23.84.1.150600.12.38.1SUSE-SU-2026:0293-1
13 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.6dtb-aarch64, kernel-64kb, kernel-docs and 8 more6.4.0-150600.23.84.1SUSE-SU-2026:0293-1
openSUSELeap 15.6kernel-default-base6.4.0-150600.23.84.1.150600.12.38.1SUSE-SU-2026:0293-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.9.1.160000.2.6openSUSE-SU-2026:20145-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.9.1openSUSE-SU-2026:20145-1
Azure Linux3kernel6.6.119.3-1AZL-72871
Alpaquita23linux-lts6.1.159-r0BELL-CVE-2025-68331
Alpaquita25linux-lts6.12.61-r0BELL-CVE-2025-68331
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-68331

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Physical removal of USB storage during I/O is the trigger. While this can happen accidentally, it can also be induced deliberately with physical access to the system.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68331.

References

Check your stackJSON