<?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-06T02:30:16.460338+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/cve-2021-46922</id>
    <title>CVE-2021-46922 — KEYS: trusted: Fix TPM reservation for seal/unseal</title>
    <updated>2026-10-06T02:30:16.476017+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>KEYS: trusted: Fix TPM reservation for seal/unseal</p>
<p>The original patch 8c657a0590de ("KEYS: trusted: Reserve TPM for seal
and unseal operations") was correct on the mailing list:</p>
<p>https://lore.kernel.org/linux-integrity/20210128235621.127925-4-jarkko@kernel.org/</p>
<p>But somehow got rebased so that the tpm_try_get_ops() in
tpm2_seal_trusted() got lost.  This causes an imbalanced put of the
TPM ops and causes oopses on TIS based hardware.</p>
<p>This fix puts back the lost tpm_try_get_ops()</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2021-46922"/>
  </entry>
</feed>
