<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T15:34:39.417946+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3288-p39f-rqpv</id>
    <title>GHSA-3288-p39f-rqpv — Unsoundness in opt-in ARMv8 assembly backend for `keccak`</title>
    <updated>2026-10-12T15:34:39.418849+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: keccak</p>
<p>### Summary</p>
<p>The `asm!` block enabled by the off-by-default `asm` feature, when enabled on ARMv8 targets, misspecified the operand
type for all of its operands, using `in` for pointers and values which were subsequently mutated by operations performed
within the assembly block.</p>
<p>### Impact</p>
<p>It's unclear what practical impact, if any, this actually had. Incorrect operand types are technically undefined
behavior, however changing them had no actual impact on the generated assembly for these targets. The possibility still
exists that it may lead to potential memory safety or other issues on hypothetical future versions of rustc.</p>
<p>### Mitigation</p>
<p>The operand types were changed from `in` to `inout`, and the impacted versions of the `keccak` crate were yanked.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3288-p39f-rqpv"/>
  </entry>
</feed>
