<?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:06:03 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99521</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99521</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rapidio: mport_cdev: fix use-after-free in mport_mm_close()&lt;/p&gt;
&lt;p&gt;A use-after-free vulnerability was identified in mport_mm_close() in
drivers/rapidio/devices/rio_mport_cdev.c, identical to the pattern
previously addressed in dma_req_free().&lt;/p&gt;
&lt;p&gt;This is observable from userspace when an application creates an mmap
mapping via the RapidIO character device and subsequently unmaps it (or
terminates, triggering exit_mmap()).  During munmap, mport_mm_close() is
invoked and drops the mapping reference via kref_put().&lt;/p&gt;
&lt;p&gt;If kref_put() drops the last reference, mport_release_mapping() is called,
which frees the underlying rio_mport_mapping structure.  The subsequent
mutex_unlock() then dereferences map-&amp;gt;md to unlock buf_mutex, leading to a
use-after-free:&lt;/p&gt;
&lt;p&gt;mport_mm_close()
     -&amp;gt; mutex_lock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);
     ...
     -&amp;gt; kref_put(&amp;amp;map-&amp;gt;ref, mport_release_mapping); /* map is freed */
     -&amp;gt; mutex_unlock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);          /* UAF: map used */&lt;/p&gt;
&lt;p&gt;Fix this by caching map-&amp;gt;md before kref_put() and using the cached pointer
for mutex unlocking, ensuring that freed memory is not accessed.&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;rapidio: mport_cdev: fix use-after-free in mport_mm_close()&lt;/p&gt;
&lt;p&gt;A use-after-free vulnerability was identified in mport_mm_close() in
drivers/rapidio/devices/rio_mport_cdev.c, identical to the pattern
previously addressed in dma_req_free().&lt;/p&gt;
&lt;p&gt;This is observable from userspace when an application creates an mmap
mapping via the RapidIO character device and subsequently unmaps it (or
terminates, triggering exit_mmap()).  During munmap, mport_mm_close() is
invoked and drops the mapping reference via kref_put().&lt;/p&gt;
&lt;p&gt;If kref_put() drops the last reference, mport_release_mapping() is called,
which frees the underlying rio_mport_mapping structure.  The subsequent
mutex_unlock() then dereferences map-&amp;gt;md to unlock buf_mutex, leading to a
use-after-free:&lt;/p&gt;
&lt;p&gt;mport_mm_close()
     -&amp;gt; mutex_lock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);
     ...
     -&amp;gt; kref_put(&amp;amp;map-&amp;gt;ref, mport_release_mapping); /* map is freed */
     -&amp;gt; mutex_unlock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);          /* UAF: map used */&lt;/p&gt;
&lt;p&gt;Fix this by caching map-&amp;gt;md before kref_put() and using the cached pointer
for mutex unlocking, ensuring that freed memory is not accessed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99521</guid>
    </item>
    <item>
      <title>GHSA-2p4q-79h9-pwgv</title>
      <link>https://db.gcve.eu/vuln/ghsa-2p4q-79h9-pwgv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rapidio: mport_cdev: fix use-after-free in mport_mm_close()&lt;/p&gt;
&lt;p&gt;A use-after-free vulnerability was identified in mport_mm_close() in
drivers/rapidio/devices/rio_mport_cdev.c, identical to the pattern
previously addressed in dma_req_free().&lt;/p&gt;
&lt;p&gt;This is observable from userspace when an application creates an mmap
mapping via the RapidIO character device and subsequently unmaps it (or
terminates, triggering exit_mmap()).  During munmap, mport_mm_close() is
invoked and drops the mapping reference via kref_put().&lt;/p&gt;
&lt;p&gt;If kref_put() drops the last reference, mport_release_mapping() is called,
which frees the underlying rio_mport_mapping structure.  The subsequent
mutex_unlock() then dereferences map-&amp;gt;md to unlock buf_mutex, leading to a
use-after-free:&lt;/p&gt;
&lt;p&gt;mport_mm_close()
     -&amp;gt; mutex_lock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);
     ...
     -&amp;gt; kref_put(&amp;amp;map-&amp;gt;ref, mport_release_mapping); /* map is freed */
     -&amp;gt; mutex_unlock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);          /* UAF: map used */&lt;/p&gt;
&lt;p&gt;Fix this by caching map-&amp;gt;md before kref_put() and using the cached pointer
for mutex unlocking, ensuring that freed memory is not accessed.&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;rapidio: mport_cdev: fix use-after-free in mport_mm_close()&lt;/p&gt;
&lt;p&gt;A use-after-free vulnerability was identified in mport_mm_close() in
drivers/rapidio/devices/rio_mport_cdev.c, identical to the pattern
previously addressed in dma_req_free().&lt;/p&gt;
&lt;p&gt;This is observable from userspace when an application creates an mmap
mapping via the RapidIO character device and subsequently unmaps it (or
terminates, triggering exit_mmap()).  During munmap, mport_mm_close() is
invoked and drops the mapping reference via kref_put().&lt;/p&gt;
&lt;p&gt;If kref_put() drops the last reference, mport_release_mapping() is called,
which frees the underlying rio_mport_mapping structure.  The subsequent
mutex_unlock() then dereferences map-&amp;gt;md to unlock buf_mutex, leading to a
use-after-free:&lt;/p&gt;
&lt;p&gt;mport_mm_close()
     -&amp;gt; mutex_lock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);
     ...
     -&amp;gt; kref_put(&amp;amp;map-&amp;gt;ref, mport_release_mapping); /* map is freed */
     -&amp;gt; mutex_unlock(&amp;amp;map-&amp;gt;md-&amp;gt;buf_mutex);          /* UAF: map used */&lt;/p&gt;
&lt;p&gt;Fix this by caching map-&amp;gt;md before kref_put() and using the cached pointer
for mutex unlocking, ensuring that freed memory is not accessed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2p4q-79h9-pwgv</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>
