<?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>Thu, 19 Nov 2026 17:39:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40096 — drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies</title>
      <link>https://db.gcve.eu/vuln/cve-2025-40096</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies&lt;/p&gt;
&lt;p&gt;When adding dependencies with drm_sched_job_add_dependency(), that
function consumes the fence reference both on success and failure, so in
the latter case the dma_fence_put() on the error path (xarray failed to
expand) is a double free.&lt;/p&gt;
&lt;p&gt;Interestingly this bug appears to have been present ever since
commit ebd5f74255b9 (&amp;#34;drm/sched: Add dependency tracking&amp;#34;), since the code
back then looked like this:&lt;/p&gt;
&lt;p&gt;drm_sched_job_add_implicit_dependencies():
...
       for (i = 0; i &amp;lt; fence_count; i++) {
               ret = drm_sched_job_add_dependency(job, fences[i]);
               if (ret)
                       break;
       }&lt;/p&gt;
&lt;p&gt;for (; i &amp;lt; fence_count; i++)
               dma_fence_put(fences[i]);&lt;/p&gt;
&lt;p&gt;Which means for the failing &amp;#39;i&amp;#39; the dma_fence_put was already a double
free. Possibly there were no users at that time, or the test cases were
insufficient to hit it.&lt;/p&gt;
&lt;p&gt;The bug was then only noticed and fixed after
commit 9c2ba265352a (&amp;#34;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2&amp;#34;)
landed, with its fixup of
commit 4eaf02d6076c (&amp;#34;drm/scheduler: fix drm_sched_job_add_implicit_dependencies&amp;#34;).&lt;/p&gt;
&lt;p&gt;At that point it was a slightly different flavour of a double free, which
commit 963d0b356935 (&amp;#34;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder&amp;#34;)
noticed and attempted to fix.&lt;/p&gt;
&lt;p&gt;But it only moved the doub…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies&lt;/p&gt;
&lt;p&gt;When adding dependencies with drm_sched_job_add_dependency(), that
function consumes the fence reference both on success and failure, so in
the latter case the dma_fence_put() on the error path (xarray failed to
expand) is a double free.&lt;/p&gt;
&lt;p&gt;Interestingly this bug appears to have been present ever since
commit ebd5f74255b9 (&amp;#34;drm/sched: Add dependency tracking&amp;#34;), since the code
back then looked like this:&lt;/p&gt;
&lt;p&gt;drm_sched_job_add_implicit_dependencies():
...
       for (i = 0; i &amp;lt; fence_count; i++) {
               ret = drm_sched_job_add_dependency(job, fences[i]);
               if (ret)
                       break;
       }&lt;/p&gt;
&lt;p&gt;for (; i &amp;lt; fence_count; i++)
               dma_fence_put(fences[i]);&lt;/p&gt;
&lt;p&gt;Which means for the failing &amp;#39;i&amp;#39; the dma_fence_put was already a double
free. Possibly there were no users at that time, or the test cases were
insufficient to hit it.&lt;/p&gt;
&lt;p&gt;The bug was then only noticed and fixed after
commit 9c2ba265352a (&amp;#34;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2&amp;#34;)
landed, with its fixup of
commit 4eaf02d6076c (&amp;#34;drm/scheduler: fix drm_sched_job_add_implicit_dependencies&amp;#34;).&lt;/p&gt;
&lt;p&gt;At that point it was a slightly different flavour of a double free, which
commit 963d0b356935 (&amp;#34;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder&amp;#34;)
noticed and attempted to fix.&lt;/p&gt;
&lt;p&gt;But it only moved the doub…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-40096</guid>
    </item>
    <item>
      <title>USN-8029-1 — linux, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8029-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: linux, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - Nios II architecture;
  - PA-RISC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Sun Sparc architecture;
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Device frequency scaling framework;
  - ARM SCMI message protocol;
  - GPIO subsystem;
  - GPU drivers;
  - Hardware monitoring drivers;
  - HW tracing;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - IOMMU subsystem;
  - ISDN/mISDN subsystem;
  - Mailbox framework;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - PCI Endpoint Test driver;
  - VMware Balloon Driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: linux, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - Nios II architecture;
  - PA-RISC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Sun Sparc architecture;
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Device frequency scaling framework;
  - ARM SCMI message protocol;
  - GPIO subsystem;
  - GPU drivers;
  - Hardware monitoring drivers;
  - HW tracing;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - IOMMU subsystem;
  - ISDN/mISDN subsystem;
  - Mailbox framework;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - PCI Endpoint Test driver;
  - VMware Balloon Driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8029-1</guid>
    </item>
  </channel>
</rss>
