<?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-04T04:57:22.884454+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-12239</id>
    <title>bdu:2025-12239</title>
    <updated>2026-10-04T04:57:22.892109+00:00</updated>
    <content>bdu:2025-12239</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-12239"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-21803</id>
    <title>BELL-CVE-2025-21803</title>
    <updated>2026-10-04T04:57:22.892145+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-2025-21803"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-314051</id>
    <title>EUVD-2026-314051</title>
    <updated>2026-10-04T04:57:22.892173+00:00</updated>
    <content>EUVD-2026-314051</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-314051"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-21803</id>
    <title>fkie_cve-2025-21803</title>
    <updated>2026-10-04T04:57:22.892185+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>LoongArch: Fix warnings during S3 suspend</p>
<p>The enable_gpe_wakeup() function calls acpi_enable_all_wakeup_gpes(),
and the later one may call the preempt_schedule_common() function,
resulting in a thread switch and causing the CPU to be in an interrupt
enabled state after the enable_gpe_wakeup() function returns, leading
to the warnings as follow.</p>
<p>[ C0] WARNING: ... at kernel/time/timekeeping.c:845 ktime_get+0xbc/0xc8
[ C0]          ...
[ C0] Call Trace:
[ C0] [&lt;90000000002243b4&gt;] show_stack+0x64/0x188
[ C0] [&lt;900000000164673c&gt;] dump_stack_lvl+0x60/0x88
[ C0] [&lt;90000000002687e4&gt;] __warn+0x8c/0x148
[ C0] [&lt;90000000015e9978&gt;] report_bug+0x1c0/0x2b0
[ C0] [&lt;90000000016478e4&gt;] do_bp+0x204/0x3b8
[ C0] [&lt;90000000025b1924&gt;] exception_handlers+0x1924/0x10000
[ C0] [&lt;9000000000343bbc&gt;] ktime_get+0xbc/0xc8
[ C0] [&lt;9000000000354c08&gt;] tick_sched_timer+0x30/0xb0
[ C0] [&lt;90000000003408e0&gt;] __hrtimer_run_queues+0x160/0x378
[ C0] [&lt;9000000000341f14&gt;] hrtimer_interrupt+0x144/0x388
[ C0] [&lt;9000000000228348&gt;] constant_timer_interrupt+0x38/0x48
[ C0] [&lt;90000000002feba4&gt;] __handle_irq_event_percpu+0x64/0x1e8
[ C0] [&lt;90000000002fed48&gt;] handle_irq_event_percpu+0x20/0x80
[ C0] [&lt;9000000000306b9c&gt;] handle_percpu_irq+0x5c/0x98
[ C0] [&lt;90000000002fd4a0&gt;] generic_handle_domain_irq+0x30/0x48
[ C0] [&lt;9000000000d0c7b0&gt;] handle_cpu_irq+0x70/0xa8
[ C0] [&lt;9000000001646b30&gt;] handle_loongarch_irq+0x30/0x48
[ C0] [&lt;9000000001646bc8&gt;] do_vint+0x…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-21803"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3vq2-wj5j-j897</id>
    <title>GHSA-3vq2-wj5j-j897</title>
    <updated>2026-10-04T04:57:22.892229+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>LoongArch: Fix warnings during S3 suspend</p>
<p>The enable_gpe_wakeup() function calls acpi_enable_all_wakeup_gpes(),
and the later one may call the preempt_schedule_common() function,
resulting in a thread switch and causing the CPU to be in an interrupt
enabled state after the enable_gpe_wakeup() function returns, leading
to the warnings as follow.</p>
<p>[ C0] WARNING: ... at kernel/time/timekeeping.c:845 ktime_get+0xbc/0xc8
[ C0]          ...
[ C0] Call Trace:
[ C0] [&lt;90000000002243b4&gt;] show_stack+0x64/0x188
[ C0] [&lt;900000000164673c&gt;] dump_stack_lvl+0x60/0x88
[ C0] [&lt;90000000002687e4&gt;] __warn+0x8c/0x148
[ C0] [&lt;90000000015e9978&gt;] report_bug+0x1c0/0x2b0
[ C0] [&lt;90000000016478e4&gt;] do_bp+0x204/0x3b8
[ C0] [&lt;90000000025b1924&gt;] exception_handlers+0x1924/0x10000
[ C0] [&lt;9000000000343bbc&gt;] ktime_get+0xbc/0xc8
[ C0] [&lt;9000000000354c08&gt;] tick_sched_timer+0x30/0xb0
[ C0] [&lt;90000000003408e0&gt;] __hrtimer_run_queues+0x160/0x378
[ C0] [&lt;9000000000341f14&gt;] hrtimer_interrupt+0x144/0x388
[ C0] [&lt;9000000000228348&gt;] constant_timer_interrupt+0x38/0x48
[ C0] [&lt;90000000002feba4&gt;] __handle_irq_event_percpu+0x64/0x1e8
[ C0] [&lt;90000000002fed48&gt;] handle_irq_event_percpu+0x20/0x80
[ C0] [&lt;9000000000306b9c&gt;] handle_percpu_irq+0x5c/0x98
[ C0] [&lt;90000000002fd4a0&gt;] generic_handle_domain_irq+0x30/0x48
[ C0] [&lt;9000000000d0c7b0&gt;] handle_cpu_irq+0x70/0xa8
[ C0] [&lt;9000000001646b30&gt;] handle_loongarch_irq+0x30/0x48
[ C0] [&lt;9000000001646bc8&gt;] do_vint+0x…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3vq2-wj5j-j897"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-1339</id>
    <title>OESA-2025-1339 — kernel security update</title>
    <updated>2026-10-04T04:57:22.892262+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>dma-debug: fix a possible deadlock on radix_lock</p>
<p>radix_lock() shouldn&amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():</p>
<p>CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash
                                                  check_sync()
                       (A) radix_lock()           (W) dma_entry_hash
dma_entry_free()
(W) radix_lock()
                       // CPU2&amp;apos;s one
                       (W) rq_lock()</p>
<p>CPU1 situation can happen when it extending radix tree and
it tries to wake up kswapd via wake_all_kswapd().</p>
<p>CPU2 situation can happen while perf_event_task_sched_out()
(i.e. dma sync operation is called while deleting perf_event using
 etm and etr tmc which are Arm Coresight hwtracing driver backends).</p>
<p>To remove this possible situation, call dma_entry_free() after
put_hash_bucket() in check_unmap().(CVE-2024-47143)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>dlm: fix possible lkb_resource null dereference</p>
<p>This patch fixes a possible null pointer dereference when this function is
called from request_lock(…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-1339"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21803</id>
    <title>UBUNTU-CVE-2025-21803</title>
    <updated>2026-10-04T04:57:22.892577+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 74 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix warnings during S3 suspend The enable_gpe_wakeup() function calls acpi_enable_all_wakeup_gpes(), and the later one may call the preempt_schedule_common() function, resulting in a thread switch and causing the CPU to be in an interrupt enabled state after the enable_gpe_wakeup() function returns, leading to the warnings as follow. [ C0] WARNING: ... at kernel/time/timekeeping.c:845 ktime_get+0xbc/0xc8 [ C0]          ... [ C0] Call Trace: [ C0] [&lt;90000000002243b4&gt;] show_stack+0x64/0x188 [ C0] [&lt;900000000164673c&gt;] dump_stack_lvl+0x60/0x88 [ C0] [&lt;90000000002687e4&gt;] __warn+0x8c/0x148 [ C0] [&lt;90000000015e9978&gt;] report_bug+0x1c0/0x2b0 [ C0] [&lt;90000000016478e4&gt;] do_bp+0x204/0x3b8 [ C0] [&lt;90000000025b1924&gt;] exception_handlers+0x1924/0x10000 [ C0] [&lt;9000000000343bbc&gt;] ktime_get+0xbc/0xc8 [ C0] [&lt;9000000000354c08&gt;] tick_sched_timer+0x30/0xb0 [ C0] [&lt;90000000003408e0&gt;] __hrtimer_run_queues+0x160/0x378 [ C0] [&lt;9000000000341f14&gt;] hrtimer_interrupt+0x144/0x388 [ C0] [&lt;9000000000228348&gt;] constant_timer_interrupt+0x38/0x48 [ C0] [&lt;90000000002feba4&gt;] __handle_irq_event_percpu+0x64/0x1e8 [ C0] [&lt;90000000002fed48&gt;] handle_irq_event_percpu+0x20/0x80 [ C0] [&lt;9000000000306b9c&gt;] handle_percpu_irq+0x5c/0x98 [ C0] [&lt;90000000002fd4a0&gt;] generic_handle_domain_irq+0x30/0x48 [ C0] [&lt;9000000000d0c7b0&gt;] handle_cpu_irq+0x70/0xa8 [ C0] [&lt;9000000001646b30&gt;] handle_loongarch_irq+0x30/0x48 [ C0] [&lt;9000000001646bc8&gt;] do_vint+0x80/…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21803"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0461</id>
    <title>WID-SEC-W-2025-0461 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T04:57:22.892691+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 durchzuführen und um nicht näher spezifizierte Auswirkungen zu erzielen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0461"/>
  </entry>
</feed>
