<?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://127.0.0.1:10001</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>Fri, 20 Nov 2026 23:50:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38165</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38165</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-38165</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>OESA-2025-2120 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2120</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;gtp: Destroy device along with udp socket&amp;amp;apos;s netns dismantle.&lt;/p&gt;
&lt;p&gt;gtp_newlink() links the device to a list in dev_net(dev) instead of
src_net, where a udp tunnel socket is created.&lt;/p&gt;
&lt;p&gt;Even when src_net is removed, the device stays alive on dev_net(dev).
Then, removing src_net triggers the splat below. [0]&lt;/p&gt;
&lt;p&gt;In this example, gtp0 is created in ns2, and the udp socket is created
in ns1.&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s link the device to the socket&amp;amp;apos;s netns instead.&lt;/p&gt;
&lt;p&gt;Now, gtp_net_exit_batch_rtnl() needs another netdev iteration to remove
all gtp devices in the netns.&lt;/p&gt;
&lt;p&gt;[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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;gtp: Destroy device along with udp socket&amp;amp;apos;s netns dismantle.&lt;/p&gt;
&lt;p&gt;gtp_newlink() links the device to a list in dev_net(dev) instead of
src_net, where a udp tunnel socket is created.&lt;/p&gt;
&lt;p&gt;Even when src_net is removed, the device stays alive on dev_net(dev).
Then, removing src_net triggers the splat below. [0]&lt;/p&gt;
&lt;p&gt;In this example, gtp0 is created in ns2, and the udp socket is created
in ns1.&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s link the device to the socket&amp;amp;apos;s netns instead.&lt;/p&gt;
&lt;p&gt;Now, gtp_net_exit_batch_rtnl() needs another netdev iteration to remove
all gtp devices in the netns.&lt;/p&gt;
&lt;p&gt;[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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2120</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38165</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38165</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix panic when calling skb_linearize The panic can be reproduced by executing the command: ./bench sockmap -c 2 -p 1 -a --rx-verdict-ingress --rx-strp 100000 Then a kernel panic was captured: &amp;#39;&amp;#39;&amp;#39; [  657.460555] kernel BUG at net/core/skbuff.c:2178! [  657.462680] Tainted: [W]=WARN [  657.463287] Workqueue: events sk_psock_backlog ... [  657.469610]  &amp;lt;TASK&amp;gt; [  657.469738]  ? die+0x36/0x90 [  657.469916]  ? do_trap+0x1d0/0x270 [  657.470118]  ? pskb_expand_head+0x612/0xf40 [  657.470376]  ? pskb_expand_head+0x612/0xf40 [  657.470620]  ? do_error_trap+0xa3/0x170 [  657.470846]  ? pskb_expand_head+0x612/0xf40 [  657.471092]  ? handle_invalid_op+0x2c/0x40 [  657.471335]  ? pskb_expand_head+0x612/0xf40 [  657.471579]  ? exc_invalid_op+0x2d/0x40 [  657.471805]  ? asm_exc_invalid_op+0x1a/0x20 [  657.472052]  ? pskb_expand_head+0xd1/0xf40 [  657.472292]  ? pskb_expand_head+0x612/0xf40 [  657.472540]  ? lock_acquire+0x18f/0x4e0 [  657.472766]  ? find_held_lock+0x2d/0x110 [  657.472999]  ? __pfx_pskb_expand_head+0x10/0x10 [  657.473263]  ? __kmalloc_cache_noprof+0x5b/0x470 [  657.473537]  ? __pfx___lock_release.isra.0+0x10/0x10 [  657.473826]  __pskb_pull_tail+0xfd/0x1d20 [  657.474062]  ? __kasan_slab_alloc+0x4e/0x90 [  657.474707]  sk_psock_skb_ingress_enqueue+0x3bf/0x510 [  657.475392]  ? __kasan_kmalloc+0xaa/0xb0 [  657.476010]  sk_psock_backlog+0x5cf/0xd70 [  657.476637]  process_one_work+0x858/0x1a2…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix panic when calling skb_linearize The panic can be reproduced by executing the command: ./bench sockmap -c 2 -p 1 -a --rx-verdict-ingress --rx-strp 100000 Then a kernel panic was captured: &amp;#39;&amp;#39;&amp;#39; [  657.460555] kernel BUG at net/core/skbuff.c:2178! [  657.462680] Tainted: [W]=WARN [  657.463287] Workqueue: events sk_psock_backlog ... [  657.469610]  &amp;lt;TASK&amp;gt; [  657.469738]  ? die+0x36/0x90 [  657.469916]  ? do_trap+0x1d0/0x270 [  657.470118]  ? pskb_expand_head+0x612/0xf40 [  657.470376]  ? pskb_expand_head+0x612/0xf40 [  657.470620]  ? do_error_trap+0xa3/0x170 [  657.470846]  ? pskb_expand_head+0x612/0xf40 [  657.471092]  ? handle_invalid_op+0x2c/0x40 [  657.471335]  ? pskb_expand_head+0x612/0xf40 [  657.471579]  ? exc_invalid_op+0x2d/0x40 [  657.471805]  ? asm_exc_invalid_op+0x1a/0x20 [  657.472052]  ? pskb_expand_head+0xd1/0xf40 [  657.472292]  ? pskb_expand_head+0x612/0xf40 [  657.472540]  ? lock_acquire+0x18f/0x4e0 [  657.472766]  ? find_held_lock+0x2d/0x110 [  657.472999]  ? __pfx_pskb_expand_head+0x10/0x10 [  657.473263]  ? __kmalloc_cache_noprof+0x5b/0x470 [  657.473537]  ? __pfx___lock_release.isra.0+0x10/0x10 [  657.473826]  __pskb_pull_tail+0xfd/0x1d20 [  657.474062]  ? __kasan_slab_alloc+0x4e/0x90 [  657.474707]  sk_psock_skb_ingress_enqueue+0x3bf/0x510 [  657.475392]  ? __kasan_kmalloc+0xaa/0xb0 [  657.476010]  sk_psock_backlog+0x5cf/0xd70 [  657.476637]  process_one_work+0x858/0x1a2…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38165</guid>
    </item>
  </channel>
</rss>
