Introduction: A recent vulnerability within the Linux kernel has been causing lock-ups and resets on some SDM845/850 devices, disrupting the performance of affected devices. In particular, the Lenovo Yoga C630 has had issues, while other devices like the Dragonboard 845c have been unaffected. A solution to this issue has been developed, and this article will provide a code snippet, links to original references, and details on the exploit.
Here's what we know about the vulnerability
The problem revolves around the pagetable walker cache coherency not working correctly across all devices in the SDM845/850 family. In the Linux kernel, this vulnerability was addressed with the following change:
`">
In the exploit, affected devices experience system lock-ups and resets, likely due to an oversight in firmware development. It appears that a change to address the issue was only introduced after the initial software release, leading to inconsistencies in cache coherency and ultimately causing crashes.
To resolve the issue, developers need to revert the change to avoid additional guesswork surrounding crashes. This can be done by reverting the following commit:
This reverts commit 6b31a9744b8726c69bbaf290f8475a368a4b805.`
Code Snippet
Revert "arm64: dts: qcom: sdm845: Affirm IDR.CCTW on apps_smmu"
This reverts commit 6b31a9744b8726c69bbaf290f8475a368a4b805.
Original References
The original commit that introduced the vulnerability can be found here.
Exploit Details
Devices affected by this vulnerability suffer from pagetable walker cache coherency issues, leading to lock-ups and resets. The initial software release for the affected devices likely serves as a baseline for their firmware, making them susceptible to crashes. By reverting the change in the Linux kernel, developers can resolve this issue and prevent further instability caused by the vulnerability.
Conclusion
CVE-2025-22012 outlines a vulnerability in the Linux kernel on some SDM845/850 devices, causing lock-ups and resets. A solution has been found by reverting a problematic commit in the kernel, ensuring stability across the affected devices. It is recommended that developers and administrators apply the provided fix to prevent further complications and crashes.
Timeline
Published on: 04/08/2025 09:15:25 UTC
Last modified on: 04/10/2025 13:10:36 UTC