<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T08:49:01.286347+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bdu:2025-11829</id>
    <title>bdu:2025-11829</title>
    <updated>2026-10-04T08:49:01.658102+00:00</updated>
    <content>bdu:2025-11829</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-11829"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-37930</id>
    <title>BELL-CVE-2025-37930</title>
    <updated>2026-10-04T08:49:01.658183+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2025-37930"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0464</id>
    <title>certfr-2025-avi-0464 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-10-04T08:49:01.658218+00:00</updated>
    <content>certfr-2025-avi-0464</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0464"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-314323</id>
    <title>EUVD-2026-314323</title>
    <updated>2026-10-04T08:49:01.658237+00:00</updated>
    <content>EUVD-2026-314323</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-314323"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37930</id>
    <title>fkie_cve-2025-37930</title>
    <updated>2026-10-04T08:49:01.658250+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>drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()</p>
<p>Nouveau is mostly designed in a way that it's expected that fences only
ever get signaled through nouveau_fence_signal(). However, in at least
one other place, nouveau_fence_done(), can signal fences, too. If that
happens (race) a signaled fence remains in the pending list for a while,
until it gets removed by nouveau_fence_update().</p>
<p>Should nouveau_fence_context_kill() run in the meantime, this would be
a bug because the function would attempt to set an error code on an
already signaled fence.</p>
<p>Have nouveau_fence_context_kill() check for a fence being signaled.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-37930"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-m44g-hq47-38xw</id>
    <title>GHSA-m44g-hq47-38xw</title>
    <updated>2026-10-04T08:49:01.658283+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>drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()</p>
<p>Nouveau is mostly designed in a way that it's expected that fences only
ever get signaled through nouveau_fence_signal(). However, in at least
one other place, nouveau_fence_done(), can signal fences, too. If that
happens (race) a signaled fence remains in the pending list for a while,
until it gets removed by nouveau_fence_update().</p>
<p>Should nouveau_fence_context_kill() run in the meantime, this would be
a bug because the function would attempt to set an error code on an
already signaled fence.</p>
<p>Have nouveau_fence_context_kill() check for a fence being signaled.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-m44g-hq47-38xw"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-37930</id>
    <title>msrc_CVE-2025-37930 — drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()</title>
    <updated>2026-10-04T08:49:01.658313+00:00</updated>
    <content>msrc_CVE-2025-37930</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-37930"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-1729</id>
    <title>OESA-2025-1729 — kernel security update</title>
    <updated>2026-10-04T08:49:01.658332+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after()irq_find_at_or_after() dereferences the interrupt descriptor which isreturned by mt_find() while neither holding sparse_irq_lock nor RCU readlock, which means the descriptor can be freed between mt_find() and thedereference:    CPU0                            CPU1    desc = mt_find()                                    delayed_free_desc(desc)    irq_desc_get_irq(desc)The use-after-free is reported by KASAN:    Call trace:     irq_get_next_irq+0x58/0x84     show_stat+0x638/0x824     seq_read_iter+0x158/0x4ec     proc_reg_read_iter+0x94/0x12c     vfs_read+0x1e0/0x2c8    Freed by task 4471:     slab_free_freelist_hook+0x174/0x1e0     __kmem_cache_free+0xa4/0x1dc     kfree+0x64/0x128     irq_kobj_release+0x28/0x3c     kobject_put+0xcc/0x1e0     delayed_free_desc+0x14/0x2c     rcu_do_batch+0x214/0x720Guard the access with a RCU read lock section.(CVE-2024-38385)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/lima: fix shared irq handling on driver remove</p>
<p>lima uses a shared interrupt, so the interrupt handlers must be prepared
to be called at any time. At driver removal time, the clocks are
disabled early and the interrupts stay registered until the very end of
the remove process due to the devm usage.
This is potentially a bug as the interrupts access…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-1729"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:01964-1</id>
    <title>SUSE-SU-2025:01964-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T08:49:01.658512+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2025:01964-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37930</id>
    <title>UBUNTU-CVE-2025-37930</title>
    <updated>2026-10-04T08:49:01.658835+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 158 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill() Nouveau is mostly designed in a way that it's expected that fences only ever get signaled through nouveau_fence_signal(). However, in at least one other place, nouveau_fence_done(), can signal fences, too. If that happens (race) a signaled fence remains in the pending list for a while, until it gets removed by nouveau_fence_update(). Should nouveau_fence_context_kill() run in the meantime, this would be a bug because the function would attempt to set an error code on an already signaled fence. Have nouveau_fence_context_kill() check for a fence being signaled.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37930"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1114</id>
    <title>WID-SEC-W-2025-1114 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T08:49:01.659408+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere nicht spezifizierte Angriffe durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1114"/>
  </entry>
</feed>
