linux-cve-announce - CVE-2025-68316: scsi: ufs: core: Fix invalid probe error return value

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025121655-CVE-2025-68316-fe36@gregkh>
Date: Tue, 16 Dec 2025 16:39:59 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68316: scsi: ufs: core: Fix invalid probe error return value

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

scsi: ufs: core: Fix invalid probe error return value

After DME Link Startup, the error return value is set to the MIPI UniPro
GenericErrorCode which can be 0 (SUCCESS) or 1 (FAILURE).  Upon failure
during driver probe, the error code 1 is propagated back to the driver
probe function which must return a negative value to indicate an error,
but 1 is not negative, so the probe is considered to be successful even
though it failed.  Subsequently, removing the driver results in an oops
because it is not in a valid state.

This happens because none of the callers of ufshcd_init() expect a
non-negative error code.

Fix the return value and documentation to match actual usage.

The Linux kernel CVE team has assigned CVE-2025-68316 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 6.13 with commit 69f5eb78d4b0cc978fe83dd2bfea1b67547290bf and fixed in 6.17.8 with commit df96dbe1af7f6591c09f862f1226d3619b07e1b6
	Issue introduced in 6.13 with commit 69f5eb78d4b0cc978fe83dd2bfea1b67547290bf and fixed in 6.18 with commit a2b32bc1d9e359a9f90d0de6af16699facb10935

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-68316
will be updated if fixes are backported, please check that for the most
up to date information about this issue.

Affected files
==============

The file(s) affected by this issue are:
	drivers/ufs/core/ufshcd.c

Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/df96dbe1af7f6591c09f862f1226d3619b07e1b6
	https://git.kernel.org/stable/c/a2b32bc1d9e359a9f90d0de6af16699facb10935