<?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-20T23:46:38.235470+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-37960</id>
    <title>BELL-CVE-2025-37960</title>
    <updated>2026-11-20T23:46:38.252231+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://127.0.0.1:10001/vuln/bell-cve-2025-37960"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0509</id>
    <title>certfr-2025-avi-0509 — 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-20T23:46:38.252334+00:00</updated>
    <content>certfr-2025-avi-0509</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0509"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-2120</id>
    <title>OESA-2025-2120 — kernel security update</title>
    <updated>2026-11-20T23:46:38.252381+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>gtp: Destroy device along with udp socket&amp;apos;s netns dismantle.</p>
<p>gtp_newlink() links the device to a list in dev_net(dev) instead of
src_net, where a udp tunnel socket is created.</p>
<p>Even when src_net is removed, the device stays alive on dev_net(dev).
Then, removing src_net triggers the splat below. [0]</p>
<p>In this example, gtp0 is created in ns2, and the udp socket is created
in ns1.</p>
<p>ip netns add ns1
  ip netns add ns2
  ip -n ns1 link add netns ns2 name gtp0 type gtp role sgsn
  ip netns del ns1</p>
<p>Let&amp;apos;s link the device to the socket&amp;apos;s netns instead.</p>
<p>Now, gtp_net_exit_batch_rtnl() needs another netdev iteration to remove
all gtp devices in the netns.</p>
<p>[0]:
ref_tracker: net notrefcnt@000000003d6e7d05 has 1/2 users at
     sk_alloc (./include/net/net_namespace.h:345 net/core/sock.c:2236)
     inet_create (net/ipv4/af_inet.c:326 net/ipv4/af_inet.c:252)
     __sock_create (net/socket.c:1558)
     udp_sock_create4 (net/ipv4/udp_tunnel_core.c:18)
     gtp_create_sock (./include/net/udp_tunnel.h:59 drivers/net/gtp.c:1423)
     gtp_create_sockets (drivers/net/gtp.c:1447)
     gtp_newlink (drivers/net/gtp.c:1507)
     rtnl_newlink (net/core/rtnetlink.c:3786 net/core/rtnetlink.c:3897 net/core/rtnetlink.c:4012)
     rtnetlink_rcv_msg (net/core/rtnetlink.c:6922)
     netlink_rcv_skb (net/netlink/af_netlink.c:2542)
     netlink_unicast…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-2120"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37960</id>
    <title>UBUNTU-CVE-2025-37960</title>
    <updated>2026-11-20T23:46:38.253082+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 120 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: memblock: Accept allocated memory before use in memblock_double_array() When increasing the array size in memblock_double_array() and the slab is not yet available, a call to memblock_find_in_range() is used to reserve/allocate memory. However, the range returned may not have been accepted, which can result in a crash when booting an SNP guest:   RIP: 0010:memcpy_orig+0x68/0x130   Code: ...   RSP: 0000:ffffffff9cc03ce8 EFLAGS: 00010006   RAX: ff11001ff83e5000 RBX: 0000000000000000 RCX: fffffffffffff000   RDX: 0000000000000bc0 RSI: ffffffff9dba8860 RDI: ff11001ff83e5c00   RBP: 0000000000002000 R08: 0000000000000000 R09: 0000000000002000   R10: 000000207fffe000 R11: 0000040000000000 R12: ffffffff9d06ef78   R13: ff11001ff83e5000 R14: ffffffff9dba7c60 R15: 0000000000000c00   memblock_double_array+0xff/0x310   memblock_add_range+0x1fb/0x2f0   memblock_reserve+0x4f/0xa0   memblock_alloc_range_nid+0xac/0x130   memblock_alloc_internal+0x53/0xc0   memblock_alloc_try_nid+0x3d/0xa0   swiotlb_init_remap+0x149/0x2f0   mem_init+0xb/0xb0   mm_core_init+0x8f/0x350   start_kernel+0x17e/0x5d0   x86_64_start_reservations+0x14/0x30   x86_64_start_kernel+0x92/0xa0   secondary_startup_64_no_verify+0x194/0x19b Mitigate this by calling accept_memory() on the memory range returned before the slab is available. Prior to v6.12, the accept_memory() interface used a 'start' and 'end' parameter instead of 'start' and 'size', therefore th…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37960"/>
  </entry>
</feed>
