Skip to main content

CVE-2025-22012: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2025-22012cvecve-2025-22012
Published: Tue Apr 08 2025 (04/08/2025, 08:18:03 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

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.

AI-Powered Analysis

AILast updated: 06/30/2025, 11:56:18 UTC

Technical Analysis

CVE-2025-22012 is a vulnerability identified in the Linux kernel specifically related to the ARM64 architecture on Qualcomm Snapdragon 845/850 devices. The issue stems from a firmware inconsistency affecting the page table walker cache coherency across these devices. The vulnerability is linked to a reverted commit (6b31a9744b8726c69bb0af290f8475a368a4b805) that initially attempted to affirm IDR0.CCTW on the apps_smmu (System Memory Management Unit) for the SDM845 platform. The problem arises because the cache coherency of the page table walker is not consistent across all SDM845/850 devices, causing system lock-ups and unexpected resets on some hardware, such as the Lenovo Yoga C630, while others like the Dragonboard 845c are unaffected. This inconsistency is attributed to a firmware development flaw where a hypervisor stack change was introduced only after the initial software release, leading to instability on devices using the earlier baseline firmware. The Linux kernel maintainers reverted the problematic commit to prevent further crashes and system instability. Although this vulnerability does not appear to be exploitable for remote code execution or privilege escalation, it can cause denial of service conditions due to system lock-ups and resets. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, the primary impact of CVE-2025-22012 is the potential for system instability and denial of service on affected ARM64-based devices running Linux kernels with the reverted commit. This could affect embedded systems, IoT devices, or specialized hardware using Qualcomm Snapdragon 845/850 chipsets, particularly in sectors relying on these platforms for critical operations such as telecommunications, industrial control, or mobile computing. The instability could lead to unexpected reboots or lock-ups, resulting in operational downtime, loss of productivity, and potential data loss if systems are not properly backed up. While the vulnerability does not directly compromise confidentiality or integrity, the availability impact could disrupt services and workflows, especially in environments where uptime is critical. Organizations using affected devices in their infrastructure or endpoint fleets may experience increased maintenance overhead and potential service interruptions until patches or firmware updates are applied.

Mitigation Recommendations

To mitigate the risks associated with CVE-2025-22012, European organizations should: 1) Identify and inventory all devices running Linux on Qualcomm Snapdragon 845/850 platforms, focusing on those using kernels containing the reverted commit. 2) Apply the latest Linux kernel updates that address this issue or revert the problematic commit as recommended by the Linux maintainers. 3) Coordinate with hardware vendors and firmware providers to obtain updated firmware or hypervisor stack versions that ensure consistent page table walker cache coherency. 4) Implement robust monitoring and alerting for system lock-ups and unexpected resets to detect potential manifestations of this vulnerability early. 5) For critical systems, consider deploying redundancy or failover mechanisms to maintain availability during unexpected device reboots. 6) Test updates in controlled environments before wide deployment to avoid regressions or compatibility issues. 7) Maintain regular backups and recovery plans to minimize data loss risks from sudden system failures. These steps go beyond generic advice by emphasizing device-specific inventory, vendor coordination, and operational continuity planning tailored to the affected hardware and software stack.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-12-29T08:45:45.805Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9833c4522896dcbe8f0f

Added to database: 5/21/2025, 9:09:07 AM

Last enriched: 6/30/2025, 11:56:18 AM

Last updated: 7/31/2025, 5:41:40 AM

Views: 10

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats