# CVE-2021-41612: Other in n/a

> Incorrect carry flag update in the ALU unit of the OpenRISC mor1kx processor can cause execution corruption in dependent software.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-qfvq-jc5r-mvjw

## What is CVE-2021-41612?

CVE-2021-41612 is a high-severity vulnerability in n/a, published on 18 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the ALU unit of the OpenRISC mor1kx processor. The carry flag is not being updated correctly for the subtract instruction, which results in an incorrect value of the carry flag. Any software that relies on this flag may experience corruption in execution.

## Which versions are affected by CVE-2021-41612?

It affects 1 product.


Products: Openrisc Mor1kx Firmware.

## How do I fix CVE-2021-41612?

No fix has been published for CVE-2021-41612 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41612 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41614](https://insights.sbomify.com/CVE-2021-41614/): Privilege escalation in n/a (high 7.8)
- [CVE-2021-41613](https://insights.sbomify.com/CVE-2021-41613/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41612 and fix it if it is affected.

What it is: CVE-2021-41612 is a high-severity vulnerability in n/a, published on 18 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41612 in the wild and no public exploit code.

Affected product: n/a. 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-2021-41612/ (Markdown: https://insights.sbomify.com/CVE-2021-41612/index.md)
```

## Sources

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

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