<?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:30:28.631008+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/fkie_cve-2026-99657</id>
    <title>fkie_cve-2026-99657</title>
    <updated>2026-11-20T21:30:28.636753+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/mmu_notifier: set -&gt;mm only after mmgrab()</p>
<p>Radeon uses a non-NULL notifier-&gt;mm to decide whether to call
mmu_interval_notifier_remove() when freeing a buffer object.
__mmu_interval_notifier_insert() sets -&gt;mm before validating the range,
so a wrapping userptr range can leave -&gt;mm set after insertion fails.
Cleanup then tries to remove an unregistered notifier for which no mm
reference was acquired.</p>
<p>Set -&gt;mm only after mmgrab(), once insertion can no longer fail. While
we could fix radeon's code instead, setting -&gt;mm on success only makes
the code more robust.</p>
<p>Fix generated by an LLM and sent by Chris Mason in private.</p>
<p>[ david: simplify description ]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99657"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-6xfq-ph85-9hwp</id>
    <title>GHSA-6xfq-ph85-9hwp</title>
    <updated>2026-11-20T21:30:28.636832+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/mmu_notifier: set -&gt;mm only after mmgrab()</p>
<p>Radeon uses a non-NULL notifier-&gt;mm to decide whether to call
mmu_interval_notifier_remove() when freeing a buffer object.
__mmu_interval_notifier_insert() sets -&gt;mm before validating the range,
so a wrapping userptr range can leave -&gt;mm set after insertion fails.
Cleanup then tries to remove an unregistered notifier for which no mm
reference was acquired.</p>
<p>Set -&gt;mm only after mmgrab(), once insertion can no longer fail. While
we could fix radeon's code instead, setting -&gt;mm on success only makes
the code more robust.</p>
<p>Fix generated by an LLM and sent by Chris Mason in private.</p>
<p>[ david: simplify description ]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-6xfq-ph85-9hwp"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:30:28.636861+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
