<?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-09-30T21:13:11.534070+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-92514</id>
    <title>CVE-2026-92514 — RDMA/erdma: Fix CEQ tasklet use-after-free on removal</title>
    <updated>2026-09-30T21:13:11.535657+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>RDMA/erdma: Fix CEQ tasklet use-after-free on removal</p>
<p>Each CEQ interrupt handler only schedules eqc-&gt;tasklet. The tasklet calls
erdma_ceq_completion_handler(), which reads the DMA-coherent EQ ring
through get_next_valid_eqe() and updates eq-&gt;dbrec through notify_eq().</p>
<p>erdma_ceqs_uninit() frees each CEQ IRQ and then destroys its EQ.
free_irq() prevents another hard IRQ and waits for an in-flight handler,
but it does not drain a tasklet that the handler already scheduled. The
tasklet can therefore access eq-&gt;qbuf or eq-&gt;dbrec after
erdma_eq_destroy() frees them.</p>
<p>Clearing ceq_cb-&gt;ready does not synchronize with a tasklet that already
passed the check at the start of erdma_ceq_completion_handler().</p>
<p>Kill the tasklet after free_irq(), when no handler can schedule it again,
and before erdma_ceq_uninit_one() releases the EQ buffers.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-92514"/>
  </entry>
</feed>
