<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 22:43:57 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-13683</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-13683</link>
      <description>cnvd-2021-13683</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-13683</guid>
    </item>
    <item>
      <title>EUVD-2026-25021</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-25021</link>
      <description>EUVD-2026-25021</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-25021</guid>
    </item>
    <item>
      <title>fkie_cve-2021-26307</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-26307</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-26307</guid>
    </item>
    <item>
      <title>GHSA-jrf8-cmgg-gv2m — Error on unsupported architectures in raw-cpuid</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jrf8-cmgg-gv2m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: raw-cpuid&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;* The CPU the program is currently running on supports the function being called.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: raw-cpuid&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;* The CPU the program is currently running on supports the function being called.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jrf8-cmgg-gv2m</guid>
    </item>
    <item>
      <title>gsd-2021-26307</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-26307</link>
      <description>gsd-2021-26307</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-26307</guid>
    </item>
    <item>
      <title>RUSTSEC-2021-0013 — Soundness issues in `raw-cpuid`</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2021-0013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: raw-cpuid&lt;/p&gt;
&lt;p&gt;## Undefined behavior in `as_string()` methods&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;See https://github.com/gz/rust-cpuid/issues/40.&lt;/p&gt;
&lt;p&gt;This flaw has been fixed in v9.0.0, by making the relevant structs
`#[repr(C)]`.&lt;/p&gt;
&lt;p&gt;## `native_cpuid::cpuid_count()` is unsound&lt;/p&gt;
&lt;p&gt;`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):&lt;/p&gt;
&lt;p&gt;&amp;gt; The CPU the program is currently running on supports the function being
&amp;gt; called.&lt;/p&gt;
&lt;p&gt;CPUID is available in most, but not all, x86/x86_64 environments. The crate
compiles only on these architectures, so others are unaffected.&lt;/p&gt;
&lt;p&gt;This issue is mitigated by the fact that affected programs are expected
to crash deterministically every time.&lt;/p&gt;
&lt;p&gt;See https://github.com/gz/rust-cpuid/issues/41.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: raw-cpuid&lt;/p&gt;
&lt;p&gt;## Undefined behavior in `as_string()` methods&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;See https://github.com/gz/rust-cpuid/issues/40.&lt;/p&gt;
&lt;p&gt;This flaw has been fixed in v9.0.0, by making the relevant structs
`#[repr(C)]`.&lt;/p&gt;
&lt;p&gt;## `native_cpuid::cpuid_count()` is unsound&lt;/p&gt;
&lt;p&gt;`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):&lt;/p&gt;
&lt;p&gt;&amp;gt; The CPU the program is currently running on supports the function being
&amp;gt; called.&lt;/p&gt;
&lt;p&gt;CPUID is available in most, but not all, x86/x86_64 environments. The crate
compiles only on these architectures, so others are unaffected.&lt;/p&gt;
&lt;p&gt;This issue is mitigated by the fact that affected programs are expected
to crash deterministically every time.&lt;/p&gt;
&lt;p&gt;See https://github.com/gz/rust-cpuid/issues/41.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2021-0013</guid>
    </item>
  </channel>
</rss>
