<?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>Sat, 21 Nov 2026 06:06:12 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:97040 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:97040</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: Denial of Service via unsafe requeue in rxrpc_recvmsg (CVE-2026-23066)
  * kernel: Kernel: Race condition in espintcp can lead to denial of service (CVE-2026-23239)
  * kernel: Linux kernel: Denial of service due to a race condition in the TLS subsystem (CVE-2026-23240)
  * kernel: Linux kernel: xfrm single-frag length not properly limited ()
  * kernel: ext4: fix e4b bitmap inconsistency reports (CVE-2026-45942)
  * kernel: Revert &amp;#34;wireguard: device: enable threaded NAPI&amp;#34; (CVE-2026-52945)
  * kernel: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset (CVE-2026-52952)
  * kernel: nfsd: fix dead ACL conflict guard in nfsd4_create (CVE-2026-53395)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nvme-pci: fix dma_vecs leak on p2p memory (CVE-2026-64020)
  * kernel: xfrm: route MIGRATE notifications to caller&amp;#39;s netns (CVE-2026-63914)
  * kernel: bpf, skmsg: fix verdict sk_data_ready racing with ktls rx (CVE-2026-64025)
  * kernel: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (CVE-2026-63987)
  * kernel: net: hsr: fix potential OOB access in supervision frame handling (CVE-2026-64000)
  * kernel: bpf: Reject fragmented frames in devmap (CVE-2026-64355)
  * kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)
  * kernel: i2c: core: fi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: Denial of Service via unsafe requeue in rxrpc_recvmsg (CVE-2026-23066)
  * kernel: Kernel: Race condition in espintcp can lead to denial of service (CVE-2026-23239)
  * kernel: Linux kernel: Denial of service due to a race condition in the TLS subsystem (CVE-2026-23240)
  * kernel: Linux kernel: xfrm single-frag length not properly limited ()
  * kernel: ext4: fix e4b bitmap inconsistency reports (CVE-2026-45942)
  * kernel: Revert &amp;#34;wireguard: device: enable threaded NAPI&amp;#34; (CVE-2026-52945)
  * kernel: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset (CVE-2026-52952)
  * kernel: nfsd: fix dead ACL conflict guard in nfsd4_create (CVE-2026-53395)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nvme-pci: fix dma_vecs leak on p2p memory (CVE-2026-64020)
  * kernel: xfrm: route MIGRATE notifications to caller&amp;#39;s netns (CVE-2026-63914)
  * kernel: bpf, skmsg: fix verdict sk_data_ready racing with ktls rx (CVE-2026-64025)
  * kernel: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (CVE-2026-63987)
  * kernel: net: hsr: fix potential OOB access in supervision frame handling (CVE-2026-64000)
  * kernel: bpf: Reject fragmented frames in devmap (CVE-2026-64355)
  * kernel: net/handshake: Take a long-lived file reference at submit (CVE-2026-64523)
  * kernel: i2c: core: fi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:97040</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-63914</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-63914</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-2026-63914</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>OESA-2026-3702 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3702</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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/9p: fix double req put in p9_fd_cancelled&lt;/p&gt;
&lt;p&gt;Syzkaller reports a KASAN issue as below:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0xfbd59c0000000021: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f]
CPU: 0 PID: 5083 Comm: syz-executor.2 Not tainted 6.1.134-syzkaller-00037-g855bd1d7d838 #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
RIP: 0010:__list_del include/linux/list.h:114 [inline]
RIP: 0010:__list_del_entry include/linux/list.h:137 [inline]
RIP: 0010:list_del include/linux/list.h:148 [inline]
RIP: 0010:p9_fd_cancelled+0xe9/0x200 net/9p/trans_fd.c:734&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 p9_client_flush+0x351/0x440 net/9p/client.c:614
 p9_client_rpc+0xb6b/0xc70 net/9p/client.c:734
 p9_client_version net/9p/client.c:920 [inline]
 p9_client_create+0xb51/0x1240 net/9p/client.c:1027
 v9fs_session_init+0x1f0/0x18f0 fs/9p/v9fs.c:408
 v9fs_mount+0xba/0xcb0 fs/9p/vfs_super.c:126
 legacy_get_tree+0x108/0x220 fs/fs_context.c:632
 vfs_get_tree+0x8e/0x300 fs/super.c:1573
 do_new_mount fs/namespace.c:3056 [inline]
 path_mount+0x6a6/0x1e90 fs/namespace.c:3386
 do_mount fs/namespace.c:3399 [inline]
 __do_sys_mount fs/namespace.c:3607 [inline]
 __se_sys_mount fs/namespace.c:3584 [inline]
 __x64_sys_mount+0x283/0x300 fs/namespace.c:358…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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/9p: fix double req put in p9_fd_cancelled&lt;/p&gt;
&lt;p&gt;Syzkaller reports a KASAN issue as below:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0xfbd59c0000000021: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f]
CPU: 0 PID: 5083 Comm: syz-executor.2 Not tainted 6.1.134-syzkaller-00037-g855bd1d7d838 #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
RIP: 0010:__list_del include/linux/list.h:114 [inline]
RIP: 0010:__list_del_entry include/linux/list.h:137 [inline]
RIP: 0010:list_del include/linux/list.h:148 [inline]
RIP: 0010:p9_fd_cancelled+0xe9/0x200 net/9p/trans_fd.c:734&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 p9_client_flush+0x351/0x440 net/9p/client.c:614
 p9_client_rpc+0xb6b/0xc70 net/9p/client.c:734
 p9_client_version net/9p/client.c:920 [inline]
 p9_client_create+0xb51/0x1240 net/9p/client.c:1027
 v9fs_session_init+0x1f0/0x18f0 fs/9p/v9fs.c:408
 v9fs_mount+0xba/0xcb0 fs/9p/vfs_super.c:126
 legacy_get_tree+0x108/0x220 fs/fs_context.c:632
 vfs_get_tree+0x8e/0x300 fs/super.c:1573
 do_new_mount fs/namespace.c:3056 [inline]
 path_mount+0x6a6/0x1e90 fs/namespace.c:3386
 do_mount fs/namespace.c:3399 [inline]
 __do_sys_mount fs/namespace.c:3607 [inline]
 __se_sys_mount fs/namespace.c:3584 [inline]
 __x64_sys_mount+0x283/0x300 fs/namespace.c:358…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3702</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63914</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63914</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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfrm: route MIGRATE notifications to caller&amp;#39;s netns xfrm_send_migrate() in net/xfrm/xfrm_user.c and pfkey_send_migrate() in net/key/af_key.c both hardcode &amp;amp;init_net for the multicast that announces a successful XFRM_MSG_MIGRATE / SADB_X_MIGRATE. XFRM_MSG_MIGRATE arrives on a per-netns NETLINK_XFRM socket, and the rest of the xfrm/af_key netlink path was made netns-aware in 2008. The other 14 multicast paths in xfrm_user.c route their event using xs_net(x), xp_net(xp) or sock_net(skb-&amp;gt;sk); only the migrate path was missed. Two consequences of the init_net hardcoding:   1. The notification (selector, old/new endpoint addresses, and the      km_address) is delivered to listeners on init_net&amp;#39;s      XFRMNLGRP_MIGRATE / pfkey BROADCAST_ALL groups rather than on      the issuing netns. An IKE daemon running in init_net therefore      receives migration notifications originating from any other      netns on the host.   2. An IKE daemon running inside a non-init netns and subscribed      to its own XFRMNLGRP_MIGRATE / pfkey groups never receives the      notification of its own migration. IKEv2 MOBIKE / address-update      handling inside a netns is silently broken. Thread struct net through km_migrate() and the xfrm_mgr.migrate function pointer, drop the &amp;amp;init_net override in xfrm_send_migrate() and pfkey_send_migrate(), and pass the caller&amp;#39;s net (already in scope in xfrm_migrate() via sock_net(skb-&amp;gt;sk)) all the way…&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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfrm: route MIGRATE notifications to caller&amp;#39;s netns xfrm_send_migrate() in net/xfrm/xfrm_user.c and pfkey_send_migrate() in net/key/af_key.c both hardcode &amp;amp;init_net for the multicast that announces a successful XFRM_MSG_MIGRATE / SADB_X_MIGRATE. XFRM_MSG_MIGRATE arrives on a per-netns NETLINK_XFRM socket, and the rest of the xfrm/af_key netlink path was made netns-aware in 2008. The other 14 multicast paths in xfrm_user.c route their event using xs_net(x), xp_net(xp) or sock_net(skb-&amp;gt;sk); only the migrate path was missed. Two consequences of the init_net hardcoding:   1. The notification (selector, old/new endpoint addresses, and the      km_address) is delivered to listeners on init_net&amp;#39;s      XFRMNLGRP_MIGRATE / pfkey BROADCAST_ALL groups rather than on      the issuing netns. An IKE daemon running in init_net therefore      receives migration notifications originating from any other      netns on the host.   2. An IKE daemon running inside a non-init netns and subscribed      to its own XFRMNLGRP_MIGRATE / pfkey groups never receives the      notification of its own migration. IKEv2 MOBIKE / address-update      handling inside a netns is silently broken. Thread struct net through km_migrate() and the xfrm_mgr.migrate function pointer, drop the &amp;amp;init_net override in xfrm_send_migrate() and pfkey_send_migrate(), and pass the caller&amp;#39;s net (already in scope in xfrm_migrate() via sock_net(skb-&amp;gt;sk)) all the way…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63914</guid>
    </item>
  </channel>
</rss>
