<?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-04T19:42:00.374783+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-07861</id>
    <title>bdu:2025-07861</title>
    <updated>2026-10-04T19:42:00.599025+00:00</updated>
    <content>bdu:2025-07861</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-07861"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2024-56613</id>
    <title>BELL-CVE-2024-56613</title>
    <updated>2026-10-04T19:42:00.599089+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2024-56613"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0254</id>
    <title>certfr-2025-avi-0254 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-10-04T19:42:00.599121+00:00</updated>
    <content>certfr-2025-avi-0254</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0254"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-313759</id>
    <title>EUVD-2026-313759</title>
    <updated>2026-10-04T19:42:00.599139+00:00</updated>
    <content>EUVD-2026-313759</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-313759"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56613</id>
    <title>fkie_cve-2024-56613</title>
    <updated>2026-10-04T19:42:00.599151+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>sched/numa: fix memory leak due to the overwritten vma-&gt;numab_state</p>
<p>[Problem Description]
When running the hackbench program of LTP, the following memory leak is
reported by kmemleak.</p>
<p># /opt/ltp/testcases/bin/hackbench 20 thread 1000
  Running with 20*40 (== 800) tasks.</p>
<p># dmesg | grep kmemleak
  ...
  kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
  kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)</p>
<p># cat /sys/kernel/debug/kmemleak
  unreferenced object 0xffff888cd8ca2c40 (size 64):
    comm "hackbench", pid 17142, jiffies 4299780315
    hex dump (first 32 bytes):
      ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace (crc bff18fd4):
      [&lt;ffffffff81419a89&gt;] __kmalloc_cache_noprof+0x2f9/0x3f0
      [&lt;ffffffff8113f715&gt;] task_numa_work+0x725/0xa00
      [&lt;ffffffff8110f878&gt;] task_work_run+0x58/0x90
      [&lt;ffffffff81ddd9f8&gt;] syscall_exit_to_user_mode+0x1c8/0x1e0
      [&lt;ffffffff81dd78d5&gt;] do_syscall_64+0x85/0x150
      [&lt;ffffffff81e0012b&gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e
  ...</p>
<p>This issue can be consistently reproduced on three different servers:
  * a 448-core server
  * a 256-core server
  * a 192-core server</p>
<p>[Root Cause]
Since multiple threads are created by the hackbench program (along with
the command argument 'thread'), a shared vma…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-56613"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qqv2-5qvx-v346</id>
    <title>GHSA-qqv2-5qvx-v346</title>
    <updated>2026-10-04T19:42:00.599202+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>sched/numa: fix memory leak due to the overwritten vma-&gt;numab_state</p>
<p>[Problem Description]
When running the hackbench program of LTP, the following memory leak is
reported by kmemleak.</p>
<p># /opt/ltp/testcases/bin/hackbench 20 thread 1000
  Running with 20*40 (== 800) tasks.</p>
<p># dmesg | grep kmemleak
  ...
  kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
  kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)</p>
<p># cat /sys/kernel/debug/kmemleak
  unreferenced object 0xffff888cd8ca2c40 (size 64):
    comm "hackbench", pid 17142, jiffies 4299780315
    hex dump (first 32 bytes):
      ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace (crc bff18fd4):
      [&lt;ffffffff81419a89&gt;] __kmalloc_cache_noprof+0x2f9/0x3f0
      [&lt;ffffffff8113f715&gt;] task_numa_work+0x725/0xa00
      [&lt;ffffffff8110f878&gt;] task_work_run+0x58/0x90
      [&lt;ffffffff81ddd9f8&gt;] syscall_exit_to_user_mode+0x1c8/0x1e0
      [&lt;ffffffff81dd78d5&gt;] do_syscall_64+0x85/0x150
      [&lt;ffffffff81e0012b&gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e
  ...</p>
<p>This issue can be consistently reproduced on three different servers:
  * a 448-core server
  * a 256-core server
  * a 192-core server</p>
<p>[Root Cause]
Since multiple threads are created by the hackbench program (along with
the command argument 'thread'), a shared vma…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qqv2-5qvx-v346"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2024-56613</id>
    <title>msrc_CVE-2024-56613 — sched/numa: fix memory leak due to the overwritten vma-&gt;numab_state</title>
    <updated>2026-10-04T19:42:00.599238+00:00</updated>
    <content>msrc_CVE-2024-56613</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2024-56613"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-1078</id>
    <title>OESA-2025-1078 — kernel security update</title>
    <updated>2026-10-04T19:42:00.599268+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: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new</p>
<p>This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().</p>
<p>Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &amp;amp;
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done(CVE-2023-52887)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()</p>
<p>Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.</p>
<p>Call stack summary:</p>
<p>[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;c…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-1078"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:02249-1</id>
    <title>SUSE-SU-2025:02249-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T19:42:00.600115+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:02249-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56613</id>
    <title>UBUNTU-CVE-2024-56613</title>
    <updated>2026-10-04T19:42:00.600189+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 105 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: sched/numa: fix memory leak due to the overwritten vma-&gt;numab_state [Problem Description] When running the hackbench program of LTP, the following memory leak is reported by kmemleak.   # /opt/ltp/testcases/bin/hackbench 20 thread 1000   Running with 20*40 (== 800) tasks.   # dmesg | grep kmemleak   ...   kmemleak: 480 new suspected memory leaks (see /sys/kernel/debug/kmemleak)   kmemleak: 665 new suspected memory leaks (see /sys/kernel/debug/kmemleak)   # cat /sys/kernel/debug/kmemleak   unreferenced object 0xffff888cd8ca2c40 (size 64):     comm "hackbench", pid 17142, jiffies 4299780315     hex dump (first 32 bytes):       ac 74 49 00 01 00 00 00 4c 84 49 00 01 00 00 00  .tI.....L.I.....       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     backtrace (crc bff18fd4):       [&lt;ffffffff81419a89&gt;] __kmalloc_cache_noprof+0x2f9/0x3f0       [&lt;ffffffff8113f715&gt;] task_numa_work+0x725/0xa00       [&lt;ffffffff8110f878&gt;] task_work_run+0x58/0x90       [&lt;ffffffff81ddd9f8&gt;] syscall_exit_to_user_mode+0x1c8/0x1e0       [&lt;ffffffff81dd78d5&gt;] do_syscall_64+0x85/0x150       [&lt;ffffffff81e0012b&gt;] entry_SYSCALL_64_after_hwframe+0x76/0x7e   ... This issue can be consistently reproduced on three different servers:   * a 448-core server   * a 256-core server   * a 192-core server [Root Cause] Since multiple threads are created by the hackbench program (along with the command argument 'thread'), a shared vma might…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56613"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</id>
    <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
    <updated>2026-10-04T19:42:00.600366+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762"/>
  </entry>
</feed>
