CVE-2025-68236: Linux kernel · PC=3
Source GCVE Database
Not known to be exploited · fixed in dd52d72f2bd727ca60c1bc9820a307b70e2154ec : update Linux kernel when convenient.
Data as of 30 Oct 2026, 16:33 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in dd52d72f2bd727ca60c1bc9820a307b70e2154ec, b712f234a74c1f5ce70b5d7aec3fc2499c258141, 5127be409c6c3815c4a7d8f6d88043e44f9b9543 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- nvd.nist.gov/vuln/detail/CVE-2025-68236 (opens in a new tab)
- git.kernel.org/stable/c/0c2619d1da8bd3d18524d69f12571a8cd7362833 (opens in a new tab)
- git.kernel.org/stable/c/1c963811b0824d0f51aabd394986589a2126f341 (opens in a new tab)
- git.kernel.org/stable/c/5127be409c6c3815c4a7d8f6d88043e44f9b9543 (opens in a new tab)
- git.kernel.org/stable/c/b712f234a74c1f5ce70b5d7aec3fc2499c258141 (opens in a new tab)
- git.kernel.org/stable/c/dd52d72f2bd727ca60c1bc9820a307b70e2154ec (opens in a new tab)