dbcve.org
Raw CpuidApplication · Raw Cpuid Project

CVE-2021-26306

HIGH · 7.5 CVSS v3.1 Published 2021-01-29
Fix available
A fix is available. Upgrade to 9.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It has unsound transmute calls within as_string() methods.

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

The raw-cpuid Rust crate before version 9.0.0 contains unsound transmute calls within its as_string() methods, violating Rust's memory safety guarantees and potentially causing undefined behavior when converting CPUID data to string representations.

MitigationUpdate the raw-cpuid crate to version 9.0.0 or later in Cargo.toml and verify no breaking changes in dependent code.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Raw CpuidApplication
Affected:< 9.0.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Locate raw-cpuid in Cargo.lock
    Search for 'name = "raw-cpuid"' in your project's Cargo.lock file and note the version number in the corresponding version = "X.X.X" field
    Affected if version is less than 9.0.0 (e.g., 8.0.0, 7.0.1, etc.)
  2. Check Cargo.toml dependency
    Inspect your Cargo.toml for 'raw-cpuid' under [dependencies] or [dev-dependencies] to see if a version is explicitly pinned
    Affected if version specifier allows versions below 9.0.0 (e.g., no version, ">=1.0", "8.0", or "<9.0")
  3. Search for as_string usage
    Run 'grep -r "as_string"' in your source code to find calls to the as_string() methods provided by raw-cpuid
    Affected if any as_string() method calls exist in your codebase and raw-cpuid version is below 9.0.0
  4. Check indirect dependencies
    Run 'cargo tree -p raw-cpuid' or 'cargo tree -i raw-cpuid' to see if raw-cpuid is pulled in as a transitive dependency and its resolved version
    Affected if raw-cpuid appears as a dependency at any level with version below 9.0.0

You are affected if raw-cpuid version resolved in Cargo.lock is below 9.0.0 and your code (or any dependent crate) invokes the as_string() methods on CPUID data structures.

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
Upgrade available Upgrade to 9.0.0 or later
Fixed in 9.0.0
Interim mitigation

Update the raw-cpuid crate to version 9.0.0 or later in Cargo.toml and verify no breaking changes in dependent code.

Fix this in Raw Cpuid Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26306 — 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-2021-26306 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