# CVE-2025-40113: remoteproc: qcom: pas: Shutdown lite ADSP DTB on X1E

> A missing shutdown sequence for the ADSP DTB firmware in the Linux kernel can cause a system crash when accessing specific memory regions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2025
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2025-40113, DEBIAN-CVE-2025-40113, GHSA-326w-gf89-vgpc, ROOT-OS-DEBIAN-13-CVE-2025-40113, UBUNTU-CVE-2025-40113

## What is CVE-2025-40113?

CVE-2025-40113 is a denial of service vulnerability in Linux, published on 12 Nov 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:

remoteproc: qcom: pas: Shutdown lite ADSP DTB on X1E

The ADSP firmware on X1E has separate firmware binaries for the main
firmware and the DTB. The same applies for the "lite" firmware loaded by
the boot firmware.

When preparing to load the new ADSP firmware we shutdown the lite_pas_id
for the main firmware, but we don't shutdown the corresponding lite pas_id
for the DTB. The fact that we're leaving it "running" forever becomes
obvious if you try to reuse (or just access) the memory region used by the
"lite" firmware: The &adsp_boot_mem is accessible, but accessing the
&adsp_boot_dtb_mem results in a crash.

We don't support reusing the memory regions currently, but nevertheless we
should not keep part of the lite firmware running. Fix this by adding the
lite_dtb_pas_id and shutting it down as well.

We don't have a way to detect if the lite firmware is actually running yet,
so ignore the return status of qcom_scm_pas_shutdown() for now. This was
already the case before, the assignment to "ret" is not used anywhere.

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


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

Apply the vendor's patch.

## Is CVE-2025-40113 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40113 is a denial of service vulnerability in Linux, published on 12 Nov 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-40113 in the wild and no public exploit code.

Affected product: Linux. 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-40113/ (Markdown: https://insights.sbomify.com/CVE-2025-40113/index.md)
```

## Sources

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

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