dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2024-44067

HIGH · 8.4 CVSS v3.1 Published 2024-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

GhostWrite is a hardware vulnerability in T-Head XuanTie C910 (TH1520 SoC) and C920 (SOPHON SG2042) RISC-V CPUs where certain CPU instructions allow unprivileged attackers to write to arbitrary physical memory locations, bypassing all software-based memory protections.

MitigationPrimary mitigation requires CPU/firmware updates from the silicon vendor; as a hardware vulnerability, software patches cannot fully remediate the issue. Implement strong process isolation, privilege separation, and consider hardware replacement if microcode updates are unavailable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify CPU model
    Run 'cat /proc/cpuinfo' or 'lscpu' and look for XuanTie C910, XuanTie C920, TH1520, or SOPHON SG2042 in the processor information
    Affected if The CPU model listed is a T-Head XuanTie C910 or C920 (or TH1520/SG2042 SoC)
  2. Check SoC/device-tree
    Examine /proc/device-tree/compatible or /sys/firmware/devicetree/base/compatible for 'xuantie,th1520' or 'sophon,sg2042' strings
    Affected if The compatible string contains 'th1520' or 'sg2042'
  3. Verify CPU ISA extensions
    Check 'cat /proc/cpuinfo' for the CPU ISA string and look for any non-standard or vendor-specific extensions that may be related to the GhostWrite vulnerability
    Affected if Non-standard Xuantie-specific extensions are present on a C910 or C920 CPU
  4. Determine privilege context
    Assess whether unprivileged code (userspace applications, containers, VMs) can execute on this system
    Affected if Unprivileged code execution is possible on affected hardware

A system is affected if it uses a T-Head XuanTie C910 or C920 CPU (TH1520 or SG2042 SoC) and permits any unprivileged code execution, as the hardware flaw allows memory writes regardless of software protections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Primary mitigation requires CPU/firmware updates from the silicon vendor; as a hardware vulnerability, software patches cannot fully remediate the issue. Implement strong process isolation, privilege separation, and consider hardware replacement if microcode updates are unavailable.

Have this fixed Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
92.0 hours of engineering $16,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $25,856.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-44067 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data