CVE-2025-37977: scsi: ufs: exynos: Disable iocc if dma-coherent property isn't set
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.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can destabilize affected Exynos-based systems using UFS storage. When a required device-tree property is absent, the driver may enable incompatible cache-sharing behavior, causing unpredictable cache-related failures. The supplied CVSS score is 7.8, reflecting potentially serious confidentiality, integrity, and availability impact under a local attack model.
Executive priority
Treat as a high-priority platform update for confirmed Exynos UFS deployments, especially systems exposed to untrusted local users. Broader Linux fleets are not automatically affected. First establish hardware and configuration applicability, then apply the vendor-supported corrected kernel through normal change controls.
Technical view
The Exynos UFS driver fails to disable IOCC shareability bits when the dma-coherent property is unset. In that configuration, descriptors are non-cacheable, so enabled shareability can create an incompatible cache configuration and random stability problems. The cited kernel changes correct the behavior by disabling IOCC for the non-coherent case.
Likely exposure
Exposure appears limited to Linux systems using the Exynos UFS driver where dma-coherent is absent. The bundle identifies affected releases including 5.16, 6.12.26, 6.14.4, and 6.15, but its version data is ambiguous. Confirm applicability against the running kernel, hardware, device tree, and vendor advisory.
Exploitation context
The supplied CVSS vector describes local access, low complexity, low privileges, and no user interaction. However, the sources provide no exploit narrative or confirmed attack path. The CVE is not listed as KEV in the bundle, so there is no supplied evidence of active exploitation.
Researcher notes
The supplied record describes random stability issues, while CVSS claims high confidentiality, integrity, and availability impact. The bundle does not explain how cache instability produces those security outcomes. No CWE, proof of concept, or exploitation evidence is provided. Researchers should distinguish affected driver configuration from generic Linux version matching.
Mitigation direction
Update to a vendor-supported kernel containing the applicable cited stable fix.
Check Linux or device-vendor guidance for the corrected release appropriate to the deployed hardware.
Prioritize affected multi-user or otherwise locally accessible systems.
Monitor unstable UFS behavior until remediation is completed.
Validation and detection
Inventory Exynos-based systems using the Linux UFS Exynos driver.
Record running kernel versions and compare them with vendor applicability guidance.
Inspect device-tree configuration to determine whether dma-coherent is absent.
Verify the installed kernel includes the applicable cited correction.
After updating, monitor storage and kernel logs for recurring UFS or cache-related instability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-37977 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.