<?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:31:04 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99726</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99726</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence&lt;/p&gt;
&lt;p&gt;v3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL
register and poll its status bits. The mutex cache_clean_lock exists to
serialize them, but v3d_clean_caches() only took the lock around its final
FLM_CLEAN write.&lt;/p&gt;
&lt;p&gt;These functions run concurrently: v3d_flush_l2t() is issued from the
BIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the
CACHE_CLEAN queue, and each queue&amp;#39;s scheduler uses its own ordered
workqueue, so their run_job callbacks execute in parallel.&lt;/p&gt;
&lt;p&gt;Because clean locked only its final write, a concurrent flush can write
L2TCACTL during clean&amp;#39;s unlocked phase. Both use non read-modify-write
writes to the one register, so whichever lands last wins: clean&amp;#39;s TMUWCF
write can land on the flush&amp;#39;s in-flight L2TFLS invalidate, triggering the
GFXH-1897 hazard of writing L2TCACTL while a flush is pending.&lt;/p&gt;
&lt;p&gt;Hold cache_clean_lock across the entire L2TCACTL access sequence so it
is fully mutually exclusive with v3d_flush_l2t(), which already takes the
lock around its own write.&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/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence&lt;/p&gt;
&lt;p&gt;v3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL
register and poll its status bits. The mutex cache_clean_lock exists to
serialize them, but v3d_clean_caches() only took the lock around its final
FLM_CLEAN write.&lt;/p&gt;
&lt;p&gt;These functions run concurrently: v3d_flush_l2t() is issued from the
BIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the
CACHE_CLEAN queue, and each queue&amp;#39;s scheduler uses its own ordered
workqueue, so their run_job callbacks execute in parallel.&lt;/p&gt;
&lt;p&gt;Because clean locked only its final write, a concurrent flush can write
L2TCACTL during clean&amp;#39;s unlocked phase. Both use non read-modify-write
writes to the one register, so whichever lands last wins: clean&amp;#39;s TMUWCF
write can land on the flush&amp;#39;s in-flight L2TFLS invalidate, triggering the
GFXH-1897 hazard of writing L2TCACTL while a flush is pending.&lt;/p&gt;
&lt;p&gt;Hold cache_clean_lock across the entire L2TCACTL access sequence so it
is fully mutually exclusive with v3d_flush_l2t(), which already takes the
lock around its own write.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99726</guid>
    </item>
    <item>
      <title>GHSA-m7r2-fj8r-2r7c</title>
      <link>https://db.gcve.eu/vuln/ghsa-m7r2-fj8r-2r7c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence&lt;/p&gt;
&lt;p&gt;v3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL
register and poll its status bits. The mutex cache_clean_lock exists to
serialize them, but v3d_clean_caches() only took the lock around its final
FLM_CLEAN write.&lt;/p&gt;
&lt;p&gt;These functions run concurrently: v3d_flush_l2t() is issued from the
BIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the
CACHE_CLEAN queue, and each queue&amp;#39;s scheduler uses its own ordered
workqueue, so their run_job callbacks execute in parallel.&lt;/p&gt;
&lt;p&gt;Because clean locked only its final write, a concurrent flush can write
L2TCACTL during clean&amp;#39;s unlocked phase. Both use non read-modify-write
writes to the one register, so whichever lands last wins: clean&amp;#39;s TMUWCF
write can land on the flush&amp;#39;s in-flight L2TFLS invalidate, triggering the
GFXH-1897 hazard of writing L2TCACTL while a flush is pending.&lt;/p&gt;
&lt;p&gt;Hold cache_clean_lock across the entire L2TCACTL access sequence so it
is fully mutually exclusive with v3d_flush_l2t(), which already takes the
lock around its own write.&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/v3d: Widen cache_clean_lock over the whole L2TCACTL sequence&lt;/p&gt;
&lt;p&gt;v3d_clean_caches() and v3d_flush_l2t() both write the single L2TCACTL
register and poll its status bits. The mutex cache_clean_lock exists to
serialize them, but v3d_clean_caches() only took the lock around its final
FLM_CLEAN write.&lt;/p&gt;
&lt;p&gt;These functions run concurrently: v3d_flush_l2t() is issued from the
BIN/RENDER/CSD invalidate path while v3d_clean_caches() runs from the
CACHE_CLEAN queue, and each queue&amp;#39;s scheduler uses its own ordered
workqueue, so their run_job callbacks execute in parallel.&lt;/p&gt;
&lt;p&gt;Because clean locked only its final write, a concurrent flush can write
L2TCACTL during clean&amp;#39;s unlocked phase. Both use non read-modify-write
writes to the one register, so whichever lands last wins: clean&amp;#39;s TMUWCF
write can land on the flush&amp;#39;s in-flight L2TFLS invalidate, triggering the
GFXH-1897 hazard of writing L2TCACTL while a flush is pending.&lt;/p&gt;
&lt;p&gt;Hold cache_clean_lock across the entire L2TCACTL access sequence so it
is fully mutually exclusive with v3d_flush_l2t(), which already takes the
lock around its own write.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-m7r2-fj8r-2r7c</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>
