# CVE-2022-31169: Cranelift vulnerable to miscompilation of constant values in division on AArch64

> A miscompilation bug in Cranelift for AArch64 causes incorrect division results in WebAssembly guest programs, affecting runtime correctness.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2022
- **Updated:** 23 Apr 2025
- **Also known as:** UBUNTU-CVE-2022-31169

## What is CVE-2022-31169?

CVE-2022-31169 is a medium-severity vulnerability in bytecodealliance wasmtime, published on 21 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wasmtime is a standalone runtime for WebAssembly. There is a bug in Wasmtime's code generator, Cranelift, for AArch64 targets where constant divisors can result in incorrect division results at runtime. This affects Wasmtime prior to version 0.38.2 and Cranelift prior to 0.85.2. This issue only affects the AArch64 platform. Other platforms are not affected. The translation rules for constants did not take into account whether sign or zero-extension should happen which resulted in an incorrect value being placed into a register when a division was encountered. The impact of this bug is that programs executing within the WebAssembly sandbox would not behave according to the WebAssembly specification. This means that it is hypothetically possible for execution within the sandbox to go awry and WebAssembly programs could produce unexpected results. This should not impact hosts executing WebAssembly but does affect the correctness of guest programs. This bug has been patched in Wasmtime version 0.38.2 and cranelift-codegen 0.85.2. There are no known workarounds.

Weakness: CWE-682 (Incorrect Calculation)

## Which versions are affected by CVE-2022-31169?

It affects 2 products.


Products: Bytecodealliance Cranelift-Codegen, Bytecodealliance Wasmtime.

## How do I fix CVE-2022-31169?

Upgrade to a fixed version.

## Is CVE-2022-31169 being exploited?

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

## Other vulnerabilities in bytecodealliance wasmtime

- [CVE-2023-26489](https://insights.sbomify.com/CVE-2023-26489/): Guest-controlled out-of-bounds read/write on x86_64 in wasmtime (critical 10.0)
- [CVE-2021-32629](https://insights.sbomify.com/CVE-2021-32629/): Memory access due to code generation flaw in Cranelift module (high 7.2)
- [CVE-2022-31146](https://insights.sbomify.com/CVE-2022-31146/): Use After Free in Wasmtime (medium 6.4)
- [CVE-2022-31104](https://insights.sbomify.com/CVE-2022-31104/): Miscompilation of `i8x16.swizzle` and `select` with v128 inputs in Wasmtime (medium 4.8)
- [CVE-2023-27477](https://insights.sbomify.com/CVE-2023-27477/): wasmtime vulnerable to miscompilation of `i8x16.select` with the same inputs on x86_64 (low 3.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31169 and fix it if it is affected.

What it is: CVE-2022-31169 is a medium-severity vulnerability in bytecodealliance wasmtime, published on 21 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31169 in the wild and no public exploit code.

Affected product: bytecodealliance wasmtime. 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-2022-31169/ (Markdown: https://insights.sbomify.com/CVE-2022-31169/index.md)
```

## Sources

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

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