scsi: ufs: ufs-qcom: Fix UFS OCP issue during UFS power down (PC=3)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.11, 6.6.160, 6.12.114, 6.17.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b61d0414136853fc38898829cde837ce5d691a9a · fixed in 1c963811b0824d0f51aabd394986589a2126f341; From b61d0414136853fc38898829cde837ce5d691a9a · fixed in 0c2619d1da8bd3d18524d69f12571a8cd7362833; From b61d0414136853fc38898829cde837ce5d691a9a · fixed in b712f234a74c1f5ce70b5d7aec3fc2499c258141; From b61d0414136853fc38898829cde837ce5d691a9a · fixed in 5127be409c6c3815c4a7d8f6d88043e44f9b9543; From 5.10.219 · fixed in 5.11
- Linux Linux
5.12
- KernelLinux
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