<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 20:48:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40096 — drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/cve-2025-40096</guid>
    </item>
    <item>
      <title>RHSA-2026:0759 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:0759</link>
      <description>&lt;p&gt;kernel: drm/i915: mark requests for GuC virtual engines to avoid use-after-free kernel: smb: client: Fix use-after-free in cifs_fill_dirent kernel: smb: client: let recv_done verify data_offset, data_length and remaining_data_length kernel: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies kernel: net: atlantic: fix fragment overflow handling in RX path&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: drm/i915: mark requests for GuC virtual engines to avoid use-after-free kernel: smb: client: Fix use-after-free in cifs_fill_dirent kernel: smb: client: let recv_done verify data_offset, data_length and remaining_data_length kernel: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies kernel: net: atlantic: fix fragment overflow handling in RX path&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:0759</guid>
    </item>
    <item>
      <title>RHSA-2026:0760 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:0760</link>
      <description>&lt;p&gt;kernel: drm/i915: mark requests for GuC virtual engines to avoid use-after-free kernel: smb: client: Fix use-after-free in cifs_fill_dirent kernel: smb: client: let recv_done verify data_offset, data_length and remaining_data_length kernel: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies kernel: net: atlantic: fix fragment overflow handling in RX path&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: drm/i915: mark requests for GuC virtual engines to avoid use-after-free kernel: smb: client: Fix use-after-free in cifs_fill_dirent kernel: smb: client: let recv_done verify data_offset, data_length and remaining_data_length kernel: drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies kernel: net: atlantic: fix fragment overflow handling in RX path&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:0760</guid>
    </item>
  </channel>
</rss>
