<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T15:25:54.469731+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-72285</id>
    <title>CVE-2026-72285 — KVM: TDX: Reject concurrent change to CPUID entry count</title>
    <updated>2026-10-02T15:25:54.600748+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>KVM: TDX: Reject concurrent change to CPUID entry count</p>
<p>Reject KVM_TDX_INIT_VM if userspace changes cpuid.nent between the
initial read and the subsequent copy of the initialization data.</p>
<p>tdx_td_init() first reads user_data-&gt;cpuid.nent to size the flexible
kvm_tdx_init_vm copy.  The copied structure also contains cpuid.nent,
and that field can differ from the value used to size the allocation if
userspace modifies the input concurrently.  setup_tdparams_cpuids() later
passes init_vm-&gt;cpuid.nent to kvm_find_cpuid_entry2(), which uses it as
the array bound for the copied entries.</p>
<p>Require the copied count to match the value used to size the allocation
so that CPUID parsing cannot access beyond the entries actually copied.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-72285"/>
  </entry>
</feed>
