scsi: ufs: exynos: Disable iocc if dma-coherent property isn't set
Affects Exynos UFS hosts on Linux kernels 5.16.0 to before 6.6.160, 6.7.0 to before 6.12.26, and 6.13.0 to before 6.14.4 whose device tree node lacks dma-coherent. Fixed in those branches.
- 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
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.6.160, 6.12.26, 6.14.4
- 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: exynos: Disable iocc if dma-coherent property isn't set If dma-coherent property isn't set then descriptors are non-cacheable and the iocc shareability bits should be disabled. Without this UFS can end up in an incompatible configuration and suffer from random cache related stability issues.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.16
- KernelLinux
From 5.16.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.26; From 6.13.0 · fixed in 6.14.4
References 5
Questions about CVE-2025-37977
What does this mean?
The Exynos UFS driver is changed to disable its iocc setting when the device tree node has no dma-coherent property. The advisory's stated condition for this case is that descriptors are then non-cacheable. The facts do not describe any further effect.Source: git.kernel.org
Am I affected, and how do I check?
Linux kernel 5.16.0 before 6.6.160, 6.7.0 before 6.12.26, and 6.13.0 before 6.14.4 are listed as affected, in setups using an Exynos UFS host. To check, run uname -r for the kernel version and look for the dma-coherent property in the Exynos UFS host node of the device tree.Source: git.kernel.org
What should I do about it?
Update to kernel 6.6.160, 6.12.26, or 6.14.4, or a later release in the matching branch.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data