https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-07T17:07:37.101767+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cnvd-2021-13684 cnvd-2021-13684 2026-10-07T17:07:37.189973+00:00 cnvd-2021-13684 https://cve.radiocsirt.org/vuln/euvd-2026-25020 EUVD-2026-25020 2026-10-07T17:07:37.190026+00:00 EUVD-2026-25020 https://cve.radiocsirt.org/vuln/fkie_cve-2021-26306 fkie_cve-2021-26306 2026-10-07T17:07:37.190044+00:00

An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It has unsound transmute calls within as_string() methods.

 https://cve.radiocsirt.org/vuln/ghsa-hvqc-pc78-x9wh GHSA-hvqc-pc78-x9wh — Soundness issue in raw-cpuid 2026-10-07T17:07:37.190075+00:00

Affected: crates.io: raw-cpuid

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. This flaw has been fixed in v9.0.0, by making the relevant structs #[repr(C)].

 https://cve.radiocsirt.org/vuln/gsd-2021-26306 gsd-2021-26306 2026-10-07T17:07:37.190101+00:00 gsd-2021-26306 https://cve.radiocsirt.org/vuln/rustsec-2021-0013 RUSTSEC-2021-0013 — Soundness issues in `raw-cpuid` 2026-10-07T17:07:37.190114+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.