<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:20:46.696829+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-99459</id>
    <title>CVE-2026-99459 — mshv_vtl: detach poll waiter on POLLFREE</title>
    <updated>2026-11-20T21:20:46.697918+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>mshv_vtl: detach poll waiter on POLLFREE</p>
<p>MSHV_SET_POLL_FILE keeps a poll wait entry after the ioctl returns. A
file reference does not always pin the registered waitqueue:
signalfd_poll() uses current-&gt;sighand-&gt;signalfd_wqh, whose lifetime is
tied to the task.</p>
<p>signalfd_cleanup() sends POLLFREE before the sighand is freed. The MSHV
callback currently leaves its entry linked, so __wake_up_pollfree()
warns and a later replacement calls remove_wait_queue() through a stale
wqh pointer. A source-equivalent KASAN run reproduced:</p>
<p>BUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave
  _raw_spin_lock_irqsave
  remove_wait_queue
  harness_ioctl [mshv_pollfree_harness]</p>
<p>The object belonged to sighand_cache and had been released through
slab_free_after_rcu_debug() after __cleanup_sighand().</p>
<p>On POLLFREE, unlink the entry under the provider waitqueue lock. Preserve
the existing CPU cancellation before publishing a NULL wqh, since a NULL
load lets a racing replacement reuse the persistent poll state. Use a
matching acquire load under RCU when removing a normal registration.</p>
<p>The callback takes no mutex and does not sleep, so the existing
mutex-to-waitqueue-lock order is unchanged.</p>
<p>An LLM assisted the source audit, fix development, and validation of this
issue.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99459"/>
  </entry>
</feed>
