https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 11:16:47 +0000 https://vulnerability.circl.lu/vuln/cve-2025-38510 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kasan: remove kasan_find_vm_area() to prevent possible deadlock</p> <p>find_vm_area() couldn&#39;t be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like:</p> <p>CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&amp;vn-&gt;busy.lock) spin_lock_bh(&amp;some_lock); &lt;interrupt occurs&gt; &lt;in softirq&gt; spin_lock(&amp;some_lock); &lt;access invalid address&gt; kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&amp;vn-&gt;busy.lock) // deadlock!</p> <p>To prevent possible deadlock while kasan reports, remove kasan_find_vm_area().</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kasan: remove kasan_find_vm_area() to prevent possible deadlock</p> <p>find_vm_area() couldn&#39;t be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like:</p> <p>CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&amp;vn-&gt;busy.lock) spin_lock_bh(&amp;some_lock); &lt;interrupt occurs&gt; &lt;in softirq&gt; spin_lock(&amp;some_lock); &lt;access invalid address&gt; kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&amp;vn-&gt;busy.lock) // deadlock!</p> <p>To prevent possible deadlock while kasan reports, remove kasan_find_vm_area().</p> https://vulnerability.circl.lu/vuln/cve-2025-38510