Most recent entries from all

cnvd-2021-13683

2026-10-07T19:46:44.905333+00:00

cnvd-2021-13683

EUVD-2026-25021

2026-10-07T19:46:44.905385+00:00

EUVD-2026-25021

fkie_cve-2021-26307

2026-10-07T19:46:44.905401+00:00

An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It allows __cpuid_count() calls even if the processor does not support the CPUID instruction, which is unsound and causes a deterministic crash.

GHSA-jrf8-cmgg-gv2m — Error on unsupported architectures in raw-cpuid

2026-10-07T19:46:44.905434+00:00

Affected: crates.io: raw-cpuid

native_cpuid::cpuid_count() exposes the unsafe __cpuid_count() intrinsic from core::arch::x86 or core::arch::x86_64 as a safe function, and uses it internally, without checking the safety requirement:

* The CPU the program is currently running on supports the function being called.

CPUID is available in most, but not all, x86/x86_64 environments. The crate compiles only on these architectures, so others are unaffected. This issue is mitigated by the fact that affected programs are expected to crash deterministically every time.

The flaw has been fixed in v9.0.0, by intentionally breaking compilation when targeting SGX or 32-bit x86 without SSE. This covers all affected CPUs.

gsd-2021-26307

2026-10-07T19:46:44.905465+00:00

gsd-2021-26307

RUSTSEC-2021-0013 — Soundness issues in `raw-cpuid`

2026-10-07T19:46:44.905477+00:00

Affected: crates.io: raw-cpuid

## Undefined behavior in `as_string()` methods

`VendorInfo::as_string()`, `SoCVendorBrand::as_string()`, and `ExtendedFunctionInfo::processor_brand_string()` construct byte slices using `std::slice::from_raw_parts()`, with data coming from `#[repr(Rust)]` structs. This is always undefined behavior.

See https://github.com/gz/rust-cpuid/issues/40.

This flaw has been fixed in v9.0.0, by making the relevant structs `#[repr(C)]`.

## `native_cpuid::cpuid_count()` is unsound

`native_cpuid::cpuid_count()` exposes the unsafe `__cpuid_count()` intrinsic from `core::arch::x86` or `core::arch::x86_64` as a safe function, and uses it internally, without checking the [safety requirement](https://doc.rust-lang.org/core/arch/index.html#overview):

> The CPU the program is currently running on supports the function being > called.

CPUID is available in most, but not all, x86/x86_64 environments. The crate compiles only on these architectures, so others are unaffected.

This issue is mitigated by the fact that affected programs are expected to crash deterministically every time.

See https://github.com/gz/rust-cpuid/issues/41.

The flaw has been fixed in v9.0.0, by intentionally breaking compilation when targeting SGX or 32-bit x86 without SSE. This covers all affected CPUs.