Linux Kernel up to 6.12.62/6.17.12/6.18.1 scsi sdev_destroy use after free

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 was found in Linux Kernel up to 6.12.62/6.17.12/6.18.1. It has been rated as critical. The impacted element is the function sdev_destroy of the component scsi. This manipulation causes use after free. This vulnerability is handled as CVE-2025-68371. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.62/6.17.12/6.18.1. It has been declared as critical. Affected by this vulnerability is the function sdev_destroy of the component scsi. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. 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: scsi: smartpqi: Fix device resources accessed after device removal Correct possible race conditions during device removal. Previously, a scheduled work item to reset a LUN could still execute after the device was removed, leading to use-after-free and other resource access issues. This race condition occurs because the abort handler may schedule a LUN reset concurrently with device removal via sdev_destroy(), leading to use-after-free and improper access to freed resources. - Check in the device reset handler if the device is still present in the controller's SCSI device list before running; if not, the reset is skipped. - Cancel any pending TMF work that has not started in sdev_destroy(). - Ensure device freeing in sdev_destroy() is done while holding the LUN reset mutex to avoid races with ongoing resets.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2025-68371 since 12/16/2025. The exploitation appears to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/12/2026).

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

Upgrading to version 6.12.63, 6.17.13, 6.18.2 or 6.19-rc1 eliminates this vulnerability. Applying the patch eccc02ba1747501d92bb2049e3ce378ba372f641/4e1acf1b6dd6dd0495bda139daafd7a403ae2dc1/1a5c5a2f88e839af5320216a02ffb075b668596a/b518e86d1a70a88f6592a7c396cf1b93493d1aab 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 (279717), EUVD (EUVD-2025-205083) and CERT Bund (WID-SEC-2025-2920). Be aware that VulDB is the high quality 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: Use after free
CWE: CWE-416 / 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: 279717
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-68371

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.63/6.17.13/6.18.2/6.19-rc1
Patch: eccc02ba1747501d92bb2049e3ce378ba372f641/4e1acf1b6dd6dd0495bda139daafd7a403ae2dc1/1a5c5a2f88e839af5320216a02ffb075b668596a/b518e86d1a70a88f6592a7c396cf1b93493d1aab

Timelineinfo

12/16/2025 CVE reserved
12/24/2025 +8 days Advisory disclosed
12/24/2025 +0 days VulDB entry created
01/12/2026 +19 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-68371 (🔒)
GCVE (CVE): GCVE-0-2025-68371
GCVE (VulDB): GCVE-100-338191
EUVD: 🔒
CERT Bund: WID-SEC-2025-2920 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 12/24/2025 15:27
Updated: 01/12/2026 05:30
Changes: 12/24/2025 15:27 (59), 12/25/2025 04:35 (2), 12/25/2025 19:56 (7), 01/12/2026 05:30 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!