<?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-04T09:32:04.955992+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:2026-06015</id>
    <title>bdu:2026-06015</title>
    <updated>2026-10-04T09:32:05.152555+00:00</updated>
    <content>bdu:2026-06015</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-06015"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-37747</id>
    <title>BELL-CVE-2025-37747</title>
    <updated>2026-10-04T09:32:05.152633+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-37747"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</id>
    <title>certfr-2025-avi-0529 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-10-04T09:32:05.152679+00:00</updated>
    <content>certfr-2025-avi-0529</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-320812</id>
    <title>EUVD-2026-320812</title>
    <updated>2026-10-04T09:32:05.152709+00:00</updated>
    <content>EUVD-2026-320812</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-320812"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37747</id>
    <title>fkie_cve-2025-37747</title>
    <updated>2026-10-04T09:32:05.152730+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>perf: Fix hang while freeing sigtrap event</p>
<p>Perf can hang while freeing a sigtrap event if a related deferred
signal hadn't managed to be sent before the file got closed:</p>
<p>perf_event_overflow()
   task_work_add(perf_pending_task)</p>
<p>fput()
   task_work_add(____fput())</p>
<p>task_work_run()
    ____fput()
        perf_release()
            perf_event_release_kernel()
                _free_event()
                    perf_pending_task_sync()
                        task_work_cancel() -&gt; FAILED
                        rcuwait_wait_event()</p>
<p>Once task_work_run() is running, the list of pending callbacks is
removed from the task_struct and from this point on task_work_cancel()
can't remove any pending and not yet started work items, hence the
task_work_cancel() failure and the hang on rcuwait_wait_event().</p>
<p>Task work could be changed to remove one work at a time, so a work
running on the current task can always cancel a pending one, however
the wait / wake design is still subject to inverted dependencies when
remote targets are involved, as pictured by Oleg:</p>
<p>T1                                                      T2</p>
<p>fd = perf_event_open(pid =&gt; T2-&gt;pid);                  fd = perf_event_open(pid =&gt; T1-&gt;pid);
close(fd)                                              close(fd)
    &lt;IRQ&gt;                                                  &lt;IRQ&gt;
    perf_event_overflow()                                  perf_event_overflow()…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-37747"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-g7p4-4259-746x</id>
    <title>GHSA-g7p4-4259-746x</title>
    <updated>2026-10-04T09:32:05.152836+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>perf: Fix hang while freeing sigtrap event</p>
<p>Perf can hang while freeing a sigtrap event if a related deferred
signal hadn't managed to be sent before the file got closed:</p>
<p>perf_event_overflow()
   task_work_add(perf_pending_task)</p>
<p>fput()
   task_work_add(____fput())</p>
<p>task_work_run()
    ____fput()
        perf_release()
            perf_event_release_kernel()
                _free_event()
                    perf_pending_task_sync()
                        task_work_cancel() -&gt; FAILED
                        rcuwait_wait_event()</p>
<p>Once task_work_run() is running, the list of pending callbacks is
removed from the task_struct and from this point on task_work_cancel()
can't remove any pending and not yet started work items, hence the
task_work_cancel() failure and the hang on rcuwait_wait_event().</p>
<p>Task work could be changed to remove one work at a time, so a work
running on the current task can always cancel a pending one, however
the wait / wake design is still subject to inverted dependencies when
remote targets are involved, as pictured by Oleg:</p>
<p>T1                                                      T2</p>
<p>fd = perf_event_open(pid =&gt; T2-&gt;pid);                  fd = perf_event_open(pid =&gt; T1-&gt;pid);
close(fd)                                              close(fd)
    &lt;IRQ&gt;                                                  &lt;IRQ&gt;
    perf_event_overflow()                                  perf_event_overflow()…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-g7p4-4259-746x"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-37747</id>
    <title>msrc_CVE-2025-37747 — perf: Fix hang while freeing sigtrap event</title>
    <updated>2026-10-04T09:32:05.152878+00:00</updated>
    <content>msrc_CVE-2025-37747</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-37747"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-1594</id>
    <title>OESA-2025-1594 — kernel security update</title>
    <updated>2026-10-04T09:32:05.152897+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:</p>
<p>net: test for not too small csum_start in virtio_net_hdr_to_skb()</p>
<p>syzbot was able to trigger this warning [1], after injecting a
malicious packet through af_packet, setting skb-&amp;gt;csum_start and thus
the transport header to an incorrect value.</p>
<p>We can at least make sure the transport header is after
the end of the network header (with a estimated minimal size).</p>
<p>[1]
[   67.873027] skb len=4096 headroom=16 headlen=14 tailroom=0
mac=(-1,-1) mac_len=0 net=(16,-6) trans=10
shinfo(txflags=0 nr_frags=1 gso(size=0 type=0 segs=0))
csum(0xa start=10 offset=0 ip_summed=3 complete_sw=0 valid=0 level=0)
hash(0x0 sw=0 l4=0) proto=0x0800 pkttype=0 iif=0
priority=0x0 mark=0x0 alloc_cpu=10 vlan_all=0x0
encapsulation=0 inner(proto=0x0000, mac=0, net=0, trans=0)
[   67.877172] dev name=veth0_vlan feat=0x000061164fdd09e9
[   67.877764] sk family=17 type=3 proto=0
[   67.878279] skb linear:   00000000: 00 00 10 00 00 00 00 00 0f 00 00 00 08 00
[   67.879128] skb frag:     00000000: 0e 00 07 00 00 00 28 00 08 80 1c 00 04 00 00 02
[   67.879877] skb frag:     00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[   67.880647] skb frag:     00000020: 00 00 02 00 00 00 08 00 1b 00 00 00 00 00 00 00
[   67.881156] skb frag:     00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[   67.881753] skb frag:     00000040: 00 00 00 00 00 00 00 00 00 00…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-1594"/>
  </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-04T09:32:05.153049+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-37747</id>
    <title>UBUNTU-CVE-2025-37747</title>
    <updated>2026-10-04T09:32:05.153262+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 150 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: perf: Fix hang while freeing sigtrap event Perf can hang while freeing a sigtrap event if a related deferred signal hadn't managed to be sent before the file got closed: perf_event_overflow()    task_work_add(perf_pending_task) fput()    task_work_add(____fput()) task_work_run()     ____fput()         perf_release()             perf_event_release_kernel()                 _free_event()                     perf_pending_task_sync()                         task_work_cancel() -&gt; FAILED                         rcuwait_wait_event() Once task_work_run() is running, the list of pending callbacks is removed from the task_struct and from this point on task_work_cancel() can't remove any pending and not yet started work items, hence the task_work_cancel() failure and the hang on rcuwait_wait_event(). Task work could be changed to remove one work at a time, so a work running on the current task can always cancel a pending one, however the wait / wake design is still subject to inverted dependencies when remote targets are involved, as pictured by Oleg: T1                                                      T2 fd = perf_event_open(pid =&gt; T2-&gt;pid);                  fd = perf_event_open(pid =&gt; T1-&gt;pid); close(fd)                                              close(fd)     &lt;IRQ&gt;                                                  &lt;IRQ&gt;     perf_event_overflow() perf_event_overflow()        task_work_add(perf_pending_task) task_…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37747"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922</id>
    <title>WID-SEC-W-2025-0922 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T09:32:05.153500+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922"/>
  </entry>
</feed>
