https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 04:36:44 +0000 https://vulnerability.circl.lu/vuln/cve-2022-49884 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: Initialize gfn_to_pfn_cache locks in dedicated helper</p> <p>Move the gfn_to_pfn_cache lock initialization to another helper and call the new helper during VM/vCPU creation. There are race conditions possible due to kvm_gfn_to_pfn_cache_init()&#39;s ability to re-initialize the cache&#39;s locks.</p> <p>For example: a race between ioctl(KVM_XEN_HVM_EVTCHN_SEND) and kvm_gfn_to_pfn_cache_init() leads to a corrupted shinfo gpc lock.</p> <p>(thread 1) | (thread 2) | kvm_xen_set_evtchn_fast | read_lock_irqsave(&amp;gpc-&gt;lock, ...) | | kvm_gfn_to_pfn_cache_init | rwlock_init(&amp;gpc-&gt;lock) read_unlock_irqrestore(&amp;gpc-&gt;lock, ...) |</p> <p>Rename &#34;cache_init&#34; and &#34;cache_destroy&#34; to activate+deactivate to avoid implying that the cache really is destroyed/freed.</p> <p>Note, there more races in the newly named kvm_gpc_activate() that will be addressed separately.</p> <p>[sean: call out that this is a bug fix]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: Initialize gfn_to_pfn_cache locks in dedicated helper</p> <p>Move the gfn_to_pfn_cache lock initialization to another helper and call the new helper during VM/vCPU creation. There are race conditions possible due to kvm_gfn_to_pfn_cache_init()&#39;s ability to re-initialize the cache&#39;s locks.</p> <p>For example: a race between ioctl(KVM_XEN_HVM_EVTCHN_SEND) and kvm_gfn_to_pfn_cache_init() leads to a corrupted shinfo gpc lock.</p> <p>(thread 1) | (thread 2) | kvm_xen_set_evtchn_fast | read_lock_irqsave(&amp;gpc-&gt;lock, ...) | | kvm_gfn_to_pfn_cache_init | rwlock_init(&amp;gpc-&gt;lock) read_unlock_irqrestore(&amp;gpc-&gt;lock, ...) |</p> <p>Rename &#34;cache_init&#34; and &#34;cache_destroy&#34; to activate+deactivate to avoid implying that the cache really is destroyed/freed.</p> <p>Note, there more races in the newly named kvm_gpc_activate() that will be addressed separately.</p> <p>[sean: call out that this is a bug fix]</p> https://vulnerability.circl.lu/vuln/cve-2022-49884