<?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>Sat, 03 Oct 2026 13:39:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-06022</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-06022</link>
      <description>bdu:2026-06022</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-06022</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53481</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53481</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53481</guid>
    </item>
    <item>
      <title>EUVD-2026-345218</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345218</link>
      <description>EUVD-2026-345218</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345218</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53481</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53481</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed&lt;/p&gt;
&lt;p&gt;Following process will trigger an infinite loop in ubi_wl_put_peb():&lt;/p&gt;
&lt;p&gt;ubifs_bgt		ubi_bgt
ubifs_leb_unmap
  ubi_leb_unmap
    ubi_eba_unmap_leb
      ubi_wl_put_peb	wear_leveling_worker
                          e1 = rb_entry(rb_first(&amp;amp;ubi-&amp;gt;used)
			  e2 = get_peb_for_wl(ubi)
			  ubi_io_read_vid_hdr  // return err (flash fault)
			  out_error:
			    ubi-&amp;gt;move_from = ubi-&amp;gt;move_to = NULL
			    wl_entry_destroy(ubi, e1)
			      ubi-&amp;gt;lookuptbl[e-&amp;gt;pnum] = NULL
      retry:
        e = ubi-&amp;gt;lookuptbl[pnum];	// return NULL
	if (e == ubi-&amp;gt;move_from) {	// NULL == NULL gets true
	  goto retry;			// infinite loop !!!&lt;/p&gt;
&lt;p&gt;$ top
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     COMMAND
  7676 root     20   0       0      0      0 R 100.0  0.0  ubifs_bgt0_0&lt;/p&gt;
&lt;p&gt;Fix it by:
 1) Letting ubi_wl_put_peb() returns directly if wearl leveling entry has
    been removed from &amp;#39;ubi-&amp;gt;lookuptbl&amp;#39;.
 2) Using &amp;#39;ubi-&amp;gt;wl_lock&amp;#39; protecting wl entry deletion to preventing an
    use-after-free problem for wl entry in ubi_wl_put_peb().&lt;/p&gt;
&lt;p&gt;Fetch a reproducer in [Link].&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed&lt;/p&gt;
&lt;p&gt;Following process will trigger an infinite loop in ubi_wl_put_peb():&lt;/p&gt;
&lt;p&gt;ubifs_bgt		ubi_bgt
ubifs_leb_unmap
  ubi_leb_unmap
    ubi_eba_unmap_leb
      ubi_wl_put_peb	wear_leveling_worker
                          e1 = rb_entry(rb_first(&amp;amp;ubi-&amp;gt;used)
			  e2 = get_peb_for_wl(ubi)
			  ubi_io_read_vid_hdr  // return err (flash fault)
			  out_error:
			    ubi-&amp;gt;move_from = ubi-&amp;gt;move_to = NULL
			    wl_entry_destroy(ubi, e1)
			      ubi-&amp;gt;lookuptbl[e-&amp;gt;pnum] = NULL
      retry:
        e = ubi-&amp;gt;lookuptbl[pnum];	// return NULL
	if (e == ubi-&amp;gt;move_from) {	// NULL == NULL gets true
	  goto retry;			// infinite loop !!!&lt;/p&gt;
&lt;p&gt;$ top
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     COMMAND
  7676 root     20   0       0      0      0 R 100.0  0.0  ubifs_bgt0_0&lt;/p&gt;
&lt;p&gt;Fix it by:
 1) Letting ubi_wl_put_peb() returns directly if wearl leveling entry has
    been removed from &amp;#39;ubi-&amp;gt;lookuptbl&amp;#39;.
 2) Using &amp;#39;ubi-&amp;gt;wl_lock&amp;#39; protecting wl entry deletion to preventing an
    use-after-free problem for wl entry in ubi_wl_put_peb().&lt;/p&gt;
&lt;p&gt;Fetch a reproducer in [Link].&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53481</guid>
    </item>
    <item>
      <title>GHSA-3pv3-rmr2-25g2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3pv3-rmr2-25g2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed&lt;/p&gt;
&lt;p&gt;Following process will trigger an infinite loop in ubi_wl_put_peb():&lt;/p&gt;
&lt;p&gt;ubifs_bgt		ubi_bgt
ubifs_leb_unmap
  ubi_leb_unmap
    ubi_eba_unmap_leb
      ubi_wl_put_peb	wear_leveling_worker
                          e1 = rb_entry(rb_first(&amp;amp;ubi-&amp;gt;used)
			  e2 = get_peb_for_wl(ubi)
			  ubi_io_read_vid_hdr  // return err (flash fault)
			  out_error:
			    ubi-&amp;gt;move_from = ubi-&amp;gt;move_to = NULL
			    wl_entry_destroy(ubi, e1)
			      ubi-&amp;gt;lookuptbl[e-&amp;gt;pnum] = NULL
      retry:
        e = ubi-&amp;gt;lookuptbl[pnum];	// return NULL
	if (e == ubi-&amp;gt;move_from) {	// NULL == NULL gets true
	  goto retry;			// infinite loop !!!&lt;/p&gt;
&lt;p&gt;$ top
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     COMMAND
  7676 root     20   0       0      0      0 R 100.0  0.0  ubifs_bgt0_0&lt;/p&gt;
&lt;p&gt;Fix it by:
 1) Letting ubi_wl_put_peb() returns directly if wearl leveling entry has
    been removed from &amp;#39;ubi-&amp;gt;lookuptbl&amp;#39;.
 2) Using &amp;#39;ubi-&amp;gt;wl_lock&amp;#39; protecting wl entry deletion to preventing an
    use-after-free problem for wl entry in ubi_wl_put_peb().&lt;/p&gt;
&lt;p&gt;Fetch a reproducer in [Link].&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed&lt;/p&gt;
&lt;p&gt;Following process will trigger an infinite loop in ubi_wl_put_peb():&lt;/p&gt;
&lt;p&gt;ubifs_bgt		ubi_bgt
ubifs_leb_unmap
  ubi_leb_unmap
    ubi_eba_unmap_leb
      ubi_wl_put_peb	wear_leveling_worker
                          e1 = rb_entry(rb_first(&amp;amp;ubi-&amp;gt;used)
			  e2 = get_peb_for_wl(ubi)
			  ubi_io_read_vid_hdr  // return err (flash fault)
			  out_error:
			    ubi-&amp;gt;move_from = ubi-&amp;gt;move_to = NULL
			    wl_entry_destroy(ubi, e1)
			      ubi-&amp;gt;lookuptbl[e-&amp;gt;pnum] = NULL
      retry:
        e = ubi-&amp;gt;lookuptbl[pnum];	// return NULL
	if (e == ubi-&amp;gt;move_from) {	// NULL == NULL gets true
	  goto retry;			// infinite loop !!!&lt;/p&gt;
&lt;p&gt;$ top
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     COMMAND
  7676 root     20   0       0      0      0 R 100.0  0.0  ubifs_bgt0_0&lt;/p&gt;
&lt;p&gt;Fix it by:
 1) Letting ubi_wl_put_peb() returns directly if wearl leveling entry has
    been removed from &amp;#39;ubi-&amp;gt;lookuptbl&amp;#39;.
 2) Using &amp;#39;ubi-&amp;gt;wl_lock&amp;#39; protecting wl entry deletion to preventing an
    use-after-free problem for wl entry in ubi_wl_put_peb().&lt;/p&gt;
&lt;p&gt;Fetch a reproducer in [Link].&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3pv3-rmr2-25g2</guid>
    </item>
    <item>
      <title>OESA-2025-2553 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2553</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/tunnel: wait until all sk_user_data reader finish before releasing the sock&lt;/p&gt;
&lt;p&gt;There is a race condition in vxlan that when deleting a vxlan device
during receiving packets, there is a possibility that the sock is
released after getting vxlan_sock vs from sk_user_data. Then in
later vxlan_ecn_decapsulate(), vxlan_get_sk_family() we will got
NULL pointer dereference. e.g.&lt;/p&gt;
&lt;p&gt;#0 [ffffa25ec6978a38] machine_kexec at ffffffff8c669757
   #1 [ffffa25ec6978a90] __crash_kexec at ffffffff8c7c0a4d
   #2 [ffffa25ec6978b58] crash_kexec at ffffffff8c7c1c48
   #3 [ffffa25ec6978b60] oops_end at ffffffff8c627f2b
   #4 [ffffa25ec6978b80] page_fault_oops at ffffffff8c678fcb
   #5 [ffffa25ec6978bd8] exc_page_fault at ffffffff8d109542
   #6 [ffffa25ec6978c00] asm_exc_page_fault at ffffffff8d200b62
      [exception RIP: vxlan_ecn_decapsulate+0x3b]
      RIP: ffffffffc1014e7b  RSP: ffffa25ec6978cb0  RFLAGS: 00010246
      RAX: 0000000000000008  RBX: ffff8aa000888000  RCX: 0000000000000000
      RDX: 000000000000000e  RSI: ffff8a9fc7ab803e  RDI: ffff8a9fd1168700
      RBP: ffff8a9fc7ab803e   R8: 0000000000700000   R9: 00000000000010ae
      R10: ffff8a9fcb748980  R11: 0000000000000000  R12: ffff8a9fd1168700
      R13: ffff8aa000888000  R14: 00000000002a0000  R15: 00000000000010ae
      ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
   #7 [ffffa25ec6978ce8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/tunnel: wait until all sk_user_data reader finish before releasing the sock&lt;/p&gt;
&lt;p&gt;There is a race condition in vxlan that when deleting a vxlan device
during receiving packets, there is a possibility that the sock is
released after getting vxlan_sock vs from sk_user_data. Then in
later vxlan_ecn_decapsulate(), vxlan_get_sk_family() we will got
NULL pointer dereference. e.g.&lt;/p&gt;
&lt;p&gt;#0 [ffffa25ec6978a38] machine_kexec at ffffffff8c669757
   #1 [ffffa25ec6978a90] __crash_kexec at ffffffff8c7c0a4d
   #2 [ffffa25ec6978b58] crash_kexec at ffffffff8c7c1c48
   #3 [ffffa25ec6978b60] oops_end at ffffffff8c627f2b
   #4 [ffffa25ec6978b80] page_fault_oops at ffffffff8c678fcb
   #5 [ffffa25ec6978bd8] exc_page_fault at ffffffff8d109542
   #6 [ffffa25ec6978c00] asm_exc_page_fault at ffffffff8d200b62
      [exception RIP: vxlan_ecn_decapsulate+0x3b]
      RIP: ffffffffc1014e7b  RSP: ffffa25ec6978cb0  RFLAGS: 00010246
      RAX: 0000000000000008  RBX: ffff8aa000888000  RCX: 0000000000000000
      RDX: 000000000000000e  RSI: ffff8a9fc7ab803e  RDI: ffff8a9fd1168700
      RBP: ffff8a9fc7ab803e   R8: 0000000000700000   R9: 00000000000010ae
      R10: ffff8a9fcb748980  R11: 0000000000000000  R12: ffff8a9fd1168700
      R13: ffff8aa000888000  R14: 00000000002a0000  R15: 00000000000010ae
      ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
   #7 [ffffa25ec6978ce8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2553</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53481</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53481</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed Following process will trigger an infinite loop in ubi_wl_put_peb(): 	ubifs_bgt		ubi_bgt ubifs_leb_unmap   ubi_leb_unmap     ubi_eba_unmap_leb       ubi_wl_put_peb	wear_leveling_worker                           e1 = rb_entry(rb_first(&amp;amp;ubi-&amp;gt;used) 			  e2 = get_peb_for_wl(ubi) 			  ubi_io_read_vid_hdr  // return err (flash fault) 			  out_error: 			    ubi-&amp;gt;move_from = ubi-&amp;gt;move_to = NULL 			    wl_entry_destroy(ubi, e1) 			      ubi-&amp;gt;lookuptbl[e-&amp;gt;pnum] = NULL       retry:         e = ubi-&amp;gt;lookuptbl[pnum];	// return NULL 	if (e == ubi-&amp;gt;move_from) {	// NULL == NULL gets true 	  goto retry;			// infinite loop !!! $ top   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     COMMAND   7676 root     20   0       0      0      0 R 100.0  0.0  ubifs_bgt0_0 Fix it by:  1) Letting ubi_wl_put_peb() returns directly if wearl leveling entry has     been removed from &amp;#39;ubi-&amp;gt;lookuptbl&amp;#39;.  2) Using &amp;#39;ubi-&amp;gt;wl_lock&amp;#39; protecting wl entry deletion to preventing an     use-after-free problem for wl entry in ubi_wl_put_peb(). Fetch a reproducer in [Link].&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed Following process will trigger an infinite loop in ubi_wl_put_peb(): 	ubifs_bgt		ubi_bgt ubifs_leb_unmap   ubi_leb_unmap     ubi_eba_unmap_leb       ubi_wl_put_peb	wear_leveling_worker                           e1 = rb_entry(rb_first(&amp;amp;ubi-&amp;gt;used) 			  e2 = get_peb_for_wl(ubi) 			  ubi_io_read_vid_hdr  // return err (flash fault) 			  out_error: 			    ubi-&amp;gt;move_from = ubi-&amp;gt;move_to = NULL 			    wl_entry_destroy(ubi, e1) 			      ubi-&amp;gt;lookuptbl[e-&amp;gt;pnum] = NULL       retry:         e = ubi-&amp;gt;lookuptbl[pnum];	// return NULL 	if (e == ubi-&amp;gt;move_from) {	// NULL == NULL gets true 	  goto retry;			// infinite loop !!! $ top   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     COMMAND   7676 root     20   0       0      0      0 R 100.0  0.0  ubifs_bgt0_0 Fix it by:  1) Letting ubi_wl_put_peb() returns directly if wearl leveling entry has     been removed from &amp;#39;ubi-&amp;gt;lookuptbl&amp;#39;.  2) Using &amp;#39;ubi-&amp;gt;wl_lock&amp;#39; protecting wl entry deletion to preventing an     use-after-free problem for wl entry in ubi_wl_put_peb(). Fetch a reproducer in [Link].&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53481</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</guid>
    </item>
  </channel>
</rss>
