<?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://vulnerability.circl.lu</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>Fri, 09 Oct 2026 15:31:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98283 — KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98283</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid()&lt;/p&gt;
&lt;p&gt;kvmhv_emulate_tlbie_all_lpid() iterates the nested-guest IDR and drops
mmu_lock before calling kvmhv_emulate_tlbie_lpid(), but does not hold a
reference on the kvm_nested_guest pointer obtained from the IDR.  A
concurrent vCPU issuing a single-LPID tlbie (is=2, ric=2) can race
through kvmhv_flush_nested() -&amp;gt; kvmhv_remove_nested() -&amp;gt; idr_remove /
--refcnt -&amp;gt; kvmhv_release_nested() -&amp;gt; kfree(gp) in that window, leaving
the iterating vCPU with a dangling pointer.  The subsequent
mutex_lock(&amp;amp;gp-&amp;gt;tlb_lock) and accesses to gp-&amp;gt;shadow_pgtable,
gp-&amp;gt;shadow_lpid and gp-&amp;gt;l1_host all touch freed memory.  The free path
is fully L1-controlled.&lt;/p&gt;
&lt;p&gt;Fix this by incrementing gp-&amp;gt;refcnt inside the loop before dropping
mmu_lock, mirroring what kvmhv_get_nested() does, and releasing the
reference with kvmhv_put_nested() after the per-guest work completes.
This is the same get/put discipline already used at every other
call site that drops mmu_lock while holding a nested-guest pointer.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid()&lt;/p&gt;
&lt;p&gt;kvmhv_emulate_tlbie_all_lpid() iterates the nested-guest IDR and drops
mmu_lock before calling kvmhv_emulate_tlbie_lpid(), but does not hold a
reference on the kvm_nested_guest pointer obtained from the IDR.  A
concurrent vCPU issuing a single-LPID tlbie (is=2, ric=2) can race
through kvmhv_flush_nested() -&amp;gt; kvmhv_remove_nested() -&amp;gt; idr_remove /
--refcnt -&amp;gt; kvmhv_release_nested() -&amp;gt; kfree(gp) in that window, leaving
the iterating vCPU with a dangling pointer.  The subsequent
mutex_lock(&amp;amp;gp-&amp;gt;tlb_lock) and accesses to gp-&amp;gt;shadow_pgtable,
gp-&amp;gt;shadow_lpid and gp-&amp;gt;l1_host all touch freed memory.  The free path
is fully L1-controlled.&lt;/p&gt;
&lt;p&gt;Fix this by incrementing gp-&amp;gt;refcnt inside the loop before dropping
mmu_lock, mirroring what kvmhv_get_nested() does, and releasing the
reference with kvmhv_put_nested() after the per-guest work completes.
This is the same get/put discipline already used at every other
call site that drops mmu_lock while holding a nested-guest pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98283</guid>
    </item>
  </channel>
</rss>
