# CVE-2025-22012: Revert "arm64: dts: qcom: sdm845: Affirm IDR0.CCTW on apps_smmu"

> A kernel regression caused system lock-ups and resets on specific Qualcomm devices due to incorrect cache coherency assumptions in the SMMU driver.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-22012, GHSA-mmrm-hwxf-8j92, UBUNTU-CVE-2025-22012

## What is CVE-2025-22012?

CVE-2025-22012 is a high-severity denial of service vulnerability in Linux kernel, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2025-22012?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-22012?

Apply the vendor's patch.

## Is CVE-2025-22012 being exploited?

There is no known exploitation of CVE-2025-22012 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22012 and fix it if it is affected.

What it is: CVE-2025-22012 is a high-severity denial of service vulnerability in Linux kernel, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22012 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22012/ (Markdown: https://insights.sbomify.com/CVE-2025-22012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22012
- OSV: https://osv.dev/vulnerability/CVE-2025-22012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22012/
Summaries are generated and may contain mistakes; the official description above is the record.