# CVE-2025-68316: scsi: ufs: core: Fix invalid probe error return value

> A logic error in the Linux kernel UFS driver causes a system crash when removing a failed driver, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68316, DEBIAN-CVE-2025-68316, GHSA-9gpm-c6g2-wrgf, UBUNTU-CVE-2025-68316

## What is CVE-2025-68316?

CVE-2025-68316 is a denial of service vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-68316?


## How do I fix CVE-2025-68316?

Apply the vendor's patch.

## Is CVE-2025-68316 being exploited?

There is no known exploitation of CVE-2025-68316 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68316 and fix it if it is affected.

What it is: CVE-2025-68316 is a denial of service vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68316 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68316/ (Markdown: https://insights.sbomify.com/CVE-2025-68316/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68316
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68316
- OSV: https://osv.dev/vulnerability/CVE-2025-68316

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68316/
Summaries are generated and may contain mistakes; the official description above is the record.