# CVE-2024-44067: Privilege escalation in n/a

> Unprivileged attackers can write to arbitrary physical memory via specific CPU instructions, enabling privilege escalation and code execution on affected RISC-V systems.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2024
- **Updated:** 20 Aug 2024
- **Also known as:** GHSA-mf26-c9w4-84w5

## What is CVE-2024-44067?

CVE-2024-44067 is a high-severity vulnerability in n/a, published on 19 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The T-Head XuanTie C910 CPU in the TH1520 SoC and the T-Head XuanTie C920 CPU in the SOPHON SG2042 have instructions that allow unprivileged attackers to write to arbitrary physical memory locations, aka GhostWrite.

Weakness: CWE-123 (Write-what-where Condition), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2024-44067?


## How do I fix CVE-2024-44067?

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

## Is CVE-2024-44067 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44067 and fix it if it is affected.

What it is: CVE-2024-44067 is a high-severity vulnerability in n/a, published on 19 Aug 2024. 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-2024-44067 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-2024-44067/ (Markdown: https://insights.sbomify.com/CVE-2024-44067/index.md)
```

## Sources

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

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