<?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://db.gcve.eu</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, 20 Nov 2026 21:30:23 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99472</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99472</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: pfncache: use a dedicated invalidation sequence for cache refresh&lt;/p&gt;
&lt;p&gt;The gfn_to_pfn_cache refresh path guards against mmu notifier
invalidations which complete while it has dropped gpc-&amp;gt;lock for the
HVA-&amp;gt;PFN lookup: hva_to_pfn_retry() samples kvm-&amp;gt;mmu_invalidate_seq
and retries if it changed, or if mn_active_invalidate_count is still
elevated.&lt;/p&gt;
&lt;p&gt;That is insufficient for HVA-based caches. mmu_invalidate_seq is only
advanced by kvm_mmu_invalidate_end() when the invalidated range
overlaps a memslot, and an HVA-based cache (e.g. the Xen shared_info
page mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backed
by any memslot at all. An invalidation of the cached HVA which starts
and ends entirely within the lookup window is thus invisible to the
retry check: mn_active_invalidate_count is back to zero and the
sequence never moved. The refresh then publishes a mapping of a page
which has already been freed, and the next reader dereferences it:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in kvm_xen_shared_info_init+0x3c6/0x440
  Read of size 4 at addr ffff8880599c2900 by task syz.2.383/7257&lt;/p&gt;
&lt;p&gt;Since gfn_to_pfn_cache_invalidate_start() deliberately skips caches
which are not currently valid (including one whose refresh is in
progress, as the refresh clears the valid flag before dropping the
lock), the retry check is the only line of defence, and it must fire
for *any* invalidation, not just those hitting a memslot.&lt;/p&gt;
&lt;p&gt;Add…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: pfncache: use a dedicated invalidation sequence for cache refresh&lt;/p&gt;
&lt;p&gt;The gfn_to_pfn_cache refresh path guards against mmu notifier
invalidations which complete while it has dropped gpc-&amp;gt;lock for the
HVA-&amp;gt;PFN lookup: hva_to_pfn_retry() samples kvm-&amp;gt;mmu_invalidate_seq
and retries if it changed, or if mn_active_invalidate_count is still
elevated.&lt;/p&gt;
&lt;p&gt;That is insufficient for HVA-based caches. mmu_invalidate_seq is only
advanced by kvm_mmu_invalidate_end() when the invalidated range
overlaps a memslot, and an HVA-based cache (e.g. the Xen shared_info
page mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backed
by any memslot at all. An invalidation of the cached HVA which starts
and ends entirely within the lookup window is thus invisible to the
retry check: mn_active_invalidate_count is back to zero and the
sequence never moved. The refresh then publishes a mapping of a page
which has already been freed, and the next reader dereferences it:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in kvm_xen_shared_info_init+0x3c6/0x440
  Read of size 4 at addr ffff8880599c2900 by task syz.2.383/7257&lt;/p&gt;
&lt;p&gt;Since gfn_to_pfn_cache_invalidate_start() deliberately skips caches
which are not currently valid (including one whose refresh is in
progress, as the refresh clears the valid flag before dropping the
lock), the retry check is the only line of defence, and it must fire
for *any* invalidation, not just those hitting a memslot.&lt;/p&gt;
&lt;p&gt;Add…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99472</guid>
    </item>
    <item>
      <title>GHSA-6cjq-7h3x-f93m</title>
      <link>https://db.gcve.eu/vuln/ghsa-6cjq-7h3x-f93m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: pfncache: use a dedicated invalidation sequence for cache refresh&lt;/p&gt;
&lt;p&gt;The gfn_to_pfn_cache refresh path guards against mmu notifier
invalidations which complete while it has dropped gpc-&amp;gt;lock for the
HVA-&amp;gt;PFN lookup: hva_to_pfn_retry() samples kvm-&amp;gt;mmu_invalidate_seq
and retries if it changed, or if mn_active_invalidate_count is still
elevated.&lt;/p&gt;
&lt;p&gt;That is insufficient for HVA-based caches. mmu_invalidate_seq is only
advanced by kvm_mmu_invalidate_end() when the invalidated range
overlaps a memslot, and an HVA-based cache (e.g. the Xen shared_info
page mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backed
by any memslot at all. An invalidation of the cached HVA which starts
and ends entirely within the lookup window is thus invisible to the
retry check: mn_active_invalidate_count is back to zero and the
sequence never moved. The refresh then publishes a mapping of a page
which has already been freed, and the next reader dereferences it:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in kvm_xen_shared_info_init+0x3c6/0x440
  Read of size 4 at addr ffff8880599c2900 by task syz.2.383/7257&lt;/p&gt;
&lt;p&gt;Since gfn_to_pfn_cache_invalidate_start() deliberately skips caches
which are not currently valid (including one whose refresh is in
progress, as the refresh clears the valid flag before dropping the
lock), the retry check is the only line of defence, and it must fire
for *any* invalidation, not just those hitting a memslot.&lt;/p&gt;
&lt;p&gt;Add…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: pfncache: use a dedicated invalidation sequence for cache refresh&lt;/p&gt;
&lt;p&gt;The gfn_to_pfn_cache refresh path guards against mmu notifier
invalidations which complete while it has dropped gpc-&amp;gt;lock for the
HVA-&amp;gt;PFN lookup: hva_to_pfn_retry() samples kvm-&amp;gt;mmu_invalidate_seq
and retries if it changed, or if mn_active_invalidate_count is still
elevated.&lt;/p&gt;
&lt;p&gt;That is insufficient for HVA-based caches. mmu_invalidate_seq is only
advanced by kvm_mmu_invalidate_end() when the invalidated range
overlaps a memslot, and an HVA-based cache (e.g. the Xen shared_info
page mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backed
by any memslot at all. An invalidation of the cached HVA which starts
and ends entirely within the lookup window is thus invisible to the
retry check: mn_active_invalidate_count is back to zero and the
sequence never moved. The refresh then publishes a mapping of a page
which has already been freed, and the next reader dereferences it:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in kvm_xen_shared_info_init+0x3c6/0x440
  Read of size 4 at addr ffff8880599c2900 by task syz.2.383/7257&lt;/p&gt;
&lt;p&gt;Since gfn_to_pfn_cache_invalidate_start() deliberately skips caches
which are not currently valid (including one whose refresh is in
progress, as the refresh clears the valid flag before dropping the
lock), the retry check is the only line of defence, and it must fire
for *any* invalidation, not just those hitting a memslot.&lt;/p&gt;
&lt;p&gt;Add…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6cjq-7h3x-f93m</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99472 — KVM: pfncache: use a dedicated invalidation sequence for cache refresh</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99472</link>
      <description>msrc_CVE-2026-99472</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99472</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
