# CVE-2025-37846: arm64: mops: Do not dereference src reg for a set operation

> A local attacker can trigger a kernel out-of-bounds access via MOPS SET operations, potentially causing a denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 9 May 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-37846, DEBIAN-CVE-2025-37846, GHSA-rjhh-hgmx-6v66, ROOT-OS-UBUNTU-2404-CVE-2025-37846, UBUNTU-CVE-2025-37846

## What is CVE-2025-37846?

CVE-2025-37846 is a high-severity vulnerability in Linux kernel, published on 9 May 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:

arm64: mops: Do not dereference src reg for a set operation

The source register is not used for SET* and reading it can result in
a UBSAN out-of-bounds array access error, specifically when the MOPS
exception is taken from a SET* sequence with XZR (reg 31) as the
source. Architecturally this is the only case where a src/dst/size
field in the ESR can be reported as 31.

Prior to 2de451a329cf662b the code in do_el0_mops() was benign as the
use of pt_regs_read_reg() prevented the out-of-bounds access.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2025-37846 being exploited?

There is no known exploitation of CVE-2025-37846 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-37846 and fix it if it is affected.

What it is: CVE-2025-37846 is a high-severity vulnerability in Linux kernel, published on 9 May 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-37846 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-37846/ (Markdown: https://insights.sbomify.com/CVE-2025-37846/index.md)
```

## Sources

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

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