<?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:03:39 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99752</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99752</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/loongson: Handle buffer mapping failures when clearing a BO&lt;/p&gt;
&lt;p&gt;lsdc_bo_clear() ignores the return value from lsdc_bo_kmap() and writes
to lbo-&amp;gt;kptr unconditionally. When the first mapping of a newly allocated
buffer fails, kptr is still NULL and the subsequent memset accesses it.&lt;/p&gt;
&lt;p&gt;Return the mapping error without touching the buffer and propagate it
from lsdc_gem_object_create(). Install the GEM object functions before
clearing so that drm_gem_object_put() can release the buffer correctly
on failure. Do not add the failed object to the tracking list or return
an uncleared buffer to the caller.&lt;/p&gt;
&lt;p&gt;Imported buffers still skip clearing, and successfully mapped buffers
are cleared and unmapped as before.&lt;/p&gt;
&lt;p&gt;Tested on LS7A2000 with a one-shot range error in ttm_bo_kmap(). Its
-EINVAL return reached userspace, the object was destroyed once, and
no GEM handle was published. Normal create/map/zero/write/read/close
cycles passed, with the tracked BO count and VRAM usage unchanged.&lt;/p&gt;
&lt;p&gt;AI assistance was used for the lifetime analysis, fix, fault-injection
tools, build and test execution.&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;drm/loongson: Handle buffer mapping failures when clearing a BO&lt;/p&gt;
&lt;p&gt;lsdc_bo_clear() ignores the return value from lsdc_bo_kmap() and writes
to lbo-&amp;gt;kptr unconditionally. When the first mapping of a newly allocated
buffer fails, kptr is still NULL and the subsequent memset accesses it.&lt;/p&gt;
&lt;p&gt;Return the mapping error without touching the buffer and propagate it
from lsdc_gem_object_create(). Install the GEM object functions before
clearing so that drm_gem_object_put() can release the buffer correctly
on failure. Do not add the failed object to the tracking list or return
an uncleared buffer to the caller.&lt;/p&gt;
&lt;p&gt;Imported buffers still skip clearing, and successfully mapped buffers
are cleared and unmapped as before.&lt;/p&gt;
&lt;p&gt;Tested on LS7A2000 with a one-shot range error in ttm_bo_kmap(). Its
-EINVAL return reached userspace, the object was destroyed once, and
no GEM handle was published. Normal create/map/zero/write/read/close
cycles passed, with the tracked BO count and VRAM usage unchanged.&lt;/p&gt;
&lt;p&gt;AI assistance was used for the lifetime analysis, fix, fault-injection
tools, build and test execution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99752</guid>
    </item>
    <item>
      <title>GHSA-x462-gw38-389q</title>
      <link>https://db.gcve.eu/vuln/ghsa-x462-gw38-389q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/loongson: Handle buffer mapping failures when clearing a BO&lt;/p&gt;
&lt;p&gt;lsdc_bo_clear() ignores the return value from lsdc_bo_kmap() and writes
to lbo-&amp;gt;kptr unconditionally. When the first mapping of a newly allocated
buffer fails, kptr is still NULL and the subsequent memset accesses it.&lt;/p&gt;
&lt;p&gt;Return the mapping error without touching the buffer and propagate it
from lsdc_gem_object_create(). Install the GEM object functions before
clearing so that drm_gem_object_put() can release the buffer correctly
on failure. Do not add the failed object to the tracking list or return
an uncleared buffer to the caller.&lt;/p&gt;
&lt;p&gt;Imported buffers still skip clearing, and successfully mapped buffers
are cleared and unmapped as before.&lt;/p&gt;
&lt;p&gt;Tested on LS7A2000 with a one-shot range error in ttm_bo_kmap(). Its
-EINVAL return reached userspace, the object was destroyed once, and
no GEM handle was published. Normal create/map/zero/write/read/close
cycles passed, with the tracked BO count and VRAM usage unchanged.&lt;/p&gt;
&lt;p&gt;AI assistance was used for the lifetime analysis, fix, fault-injection
tools, build and test execution.&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;drm/loongson: Handle buffer mapping failures when clearing a BO&lt;/p&gt;
&lt;p&gt;lsdc_bo_clear() ignores the return value from lsdc_bo_kmap() and writes
to lbo-&amp;gt;kptr unconditionally. When the first mapping of a newly allocated
buffer fails, kptr is still NULL and the subsequent memset accesses it.&lt;/p&gt;
&lt;p&gt;Return the mapping error without touching the buffer and propagate it
from lsdc_gem_object_create(). Install the GEM object functions before
clearing so that drm_gem_object_put() can release the buffer correctly
on failure. Do not add the failed object to the tracking list or return
an uncleared buffer to the caller.&lt;/p&gt;
&lt;p&gt;Imported buffers still skip clearing, and successfully mapped buffers
are cleared and unmapped as before.&lt;/p&gt;
&lt;p&gt;Tested on LS7A2000 with a one-shot range error in ttm_bo_kmap(). Its
-EINVAL return reached userspace, the object was destroyed once, and
no GEM handle was published. Normal create/map/zero/write/read/close
cycles passed, with the tracked BO count and VRAM usage unchanged.&lt;/p&gt;
&lt;p&gt;AI assistance was used for the lifetime analysis, fix, fault-injection
tools, build and test execution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-x462-gw38-389q</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>
