<?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://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T05:51:32.357893+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/bell-cve-2025-21716</id>
    <title>BELL-CVE-2025-21716</title>
    <updated>2026-11-21T05:51:32.366085+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://127.0.0.1:10001/vuln/bell-cve-2025-21716"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0212</id>
    <title>certfr-2025-avi-0212 — 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-11-21T05:51:32.366120+00:00</updated>
    <content>certfr-2025-avi-0212</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0212"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1339</id>
    <title>OESA-2025-1339 — kernel security update</title>
    <updated>2026-11-21T05:51:32.366137+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://127.0.0.1:10001/vuln/oesa-2025-1339"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21716</id>
    <title>UBUNTU-CVE-2025-21716</title>
    <updated>2026-11-21T05:51:32.366598+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 106 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix uninit-value in vxlan_vnifilter_dump() KMSAN reported an uninit-value access in vxlan_vnifilter_dump() [1]. If the length of the netlink message payload is less than sizeof(struct tunnel_msg), vxlan_vnifilter_dump() accesses bytes beyond the message. This can lead to uninit-value access. Fix this by returning an error in such situations. [1] BUG: KMSAN: uninit-value in vxlan_vnifilter_dump+0x328/0x920 drivers/net/vxlan/vxlan_vnifilter.c:422  vxlan_vnifilter_dump+0x328/0x920 drivers/net/vxlan/vxlan_vnifilter.c:422  rtnl_dumpit+0xd5/0x2f0 net/core/rtnetlink.c:6786  netlink_dump+0x93e/0x15f0 net/netlink/af_netlink.c:2317  __netlink_dump_start+0x716/0xd60 net/netlink/af_netlink.c:2432  netlink_dump_start include/linux/netlink.h:340 [inline]  rtnetlink_dump_start net/core/rtnetlink.c:6815 [inline]  rtnetlink_rcv_msg+0x1256/0x14a0 net/core/rtnetlink.c:6882  netlink_rcv_skb+0x467/0x660 net/netlink/af_netlink.c:2542  rtnetlink_rcv+0x35/0x40 net/core/rtnetlink.c:6944  netlink_unicast_kernel net/netlink/af_netlink.c:1321 [inline]  netlink_unicast+0xed6/0x1290 net/netlink/af_netlink.c:1347  netlink_sendmsg+0x1092/0x1230 net/netlink/af_netlink.c:1891  sock_sendmsg_nosec net/socket.c:711 [inline]  __sock_sendmsg+0x330/0x3d0 net/socket.c:726  ____sys_sendmsg+0x7f4/0xb50 net/socket.c:2583  ___sys_sendmsg+0x271/0x3b0 net/socket.c:2637  __sys_sendmsg net/socket.c:2669 [inline]  __do_sys_sendmsg net/socket.c:2674 […</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21716"/>
  </entry>
</feed>
