CVE-2025-22012: Revert "arm64: dts: qcom: sdm845: Affirm IDR0.CCTW on apps_smmu"
In the Linux kernel, the following vulnerability has been resolved:
Revert "arm64: dts: qcom: sdm845: Affirm IDR0.CCTW on apps_smmu"
There are reports that the pagetable walker cache coherency is not a
given across the spectrum of SDM845/850 devices, leading to lock-ups
and resets. It works fine on some devices (like the Dragonboard 845c,
but not so much on the Lenovo Yoga C630).
This unfortunately looks like a fluke in firmware development, where
likely somewhere in the vast hypervisor stack, a change to accommodate
for this was only introduced after the initial software release (which
often serves as a baseline for products).
Revert the change to avoid additional guesswork around crashes.
This reverts commit 6b31a9744b8726c69bb0af290f8475a368a4b805.
Security readout for executives and security teams
Plain-English summary
A Linux hardware-description change assumed memory-translation hardware was cache-coherent. On some Qualcomm SDM845/850 devices, that assumption is false and can cause system lockups or unexpected resets. Linux resolved the issue by reversing the change.
Executive priority
Treat this as high priority where SDM845/850 Linux devices are deployed, particularly systems experiencing unexplained resets. Scope the fleet promptly and remediate through accelerated maintenance. The local-access requirement and absence of documented active exploitation reduce broad external urgency, but recurring lockups can materially disrupt operations.
Technical view
The affected device-tree setting affirms IDR0.CCTW for apps_smmu. Where the firmware or hypervisor stack does not provide the expected page-table walker cache coherency, systems can lock up or reset. The bundle lists Linux 6.13–6.13.9 and 6.14 as affected and classifies the issue as CWE-667.
Likely exposure
Exposure appears limited to Linux systems using Qualcomm SDM845/850 with the affected apps_smmu change and incompatible firmware behavior. The Dragonboard 845c reportedly works while the Lenovo Yoga C630 does not, so version alone cannot prove exposure. Distribution backports require vendor confirmation.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. This CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation. They directly document lockups and resets, not a demonstrated confidentiality or integrity attack.
Researcher notes
Public evidence establishes a hardware- and firmware-dependent coherency regression corrected by reverting a kernel commit. It does not demonstrate exploitation or substantiate confidentiality and integrity compromise beyond the CVSS assessment. Exact affected distribution builds and fixed package versions are not supplied, making vendor backport verification essential.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable reversion or an equivalent backport.
Prioritize affected SDM845/850 devices experiencing unexplained lockups or resets.
Check distribution and device-vendor advisories for exact fixed package and firmware applicability.
If no packaged fix exists, seek vendor guidance; the sources provide no alternative workaround.
Validation and detection
Inventory kernel versions, device models, and Qualcomm SoCs across the fleet.
Verify kernel changelogs or source packages include a referenced reversion or equivalent vendor backport.
Review historical lockup and reset incidents on potentially affected devices.
After updating, test system stability and normal SMMU-dependent workloads.
Confirm fixed-package mappings with the relevant Linux distribution or device vendor.
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.
cwe · low confidence lookup
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.