Linux Kernel up to 6.17.10 SCSI Driver uas.c dma_direct_unmap_sg memory corruption

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.6$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in Linux Kernel up to 6.17.10. This issue affects the function dma_direct_unmap_sg of the file uas.c of the component SCSI Driver. Such manipulation leads to memory corruption. This vulnerability is listed as CVE-2025-68331. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.17.10 and classified as critical. Affected by this issue is the function dma_direct_unmap_sg of the file uas.c of the component SCSI Driver. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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().

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2025-68331 since 12/16/2025. The exploitation is known to be easy. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 12/23/2025).

The vulnerability scanner Nessus provides a plugin with the ID 279577 (Linux Distros Unpatched Vulnerability : CVE-2025-68331), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.247, 5.15.197, 6.1.159, 6.6.119, 6.12.61 or 6.17.11 eliminates this vulnerability. Applying the patch 6289fc489e94c9beb6be2b502ccc263663733d72/66ac05e7b0d6bbd1bee9fcf729e20fd4cce86d17/75f8e2643085db4f7e136fc6b368eb114dd80a64/e3a55221f4de080cb7a91ba10f01c4f708603f8d/2b90a8131c83f6f2be69397d2b7d14d217d95d2f/426edbfc88b22601ea34a441a469092e7b301c52/26d56a9fcb2014b99e654127960aa0a48a391e3c is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (279577) and CERT Bund (WID-SEC-2025-2914). Once again VulDB remains the best source for vulnerability data.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 279577
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-68331

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.247/5.15.197/6.1.159/6.6.119/6.12.61/6.17.11
Patch: 6289fc489e94c9beb6be2b502ccc263663733d72/66ac05e7b0d6bbd1bee9fcf729e20fd4cce86d17/75f8e2643085db4f7e136fc6b368eb114dd80a64/e3a55221f4de080cb7a91ba10f01c4f708603f8d/2b90a8131c83f6f2be69397d2b7d14d217d95d2f/426edbfc88b22601ea34a441a469092e7b301c52/26d56a9fcb2014b99e654127960aa0a48a391e3c

Timelineinfo

12/16/2025 CVE reserved
12/22/2025 +6 days Advisory disclosed
12/22/2025 +0 days VulDB entry created
12/23/2025 +1 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-68331 (🔒)
GCVE (CVE): GCVE-0-2025-68331
GCVE (VulDB): GCVE-100-337748
CERT Bund: WID-SEC-2025-2914 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 12/22/2025 18:20
Updated: 12/23/2025 13:30
Changes: 12/22/2025 18:20 (60), 12/23/2025 08:19 (2), 12/23/2025 13:30 (7)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!