<?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 02:02:33 +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-64025</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64025</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-64025</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-3704 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3704</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: 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: hns3: add VLAN id validation before using&lt;/p&gt;
&lt;p&gt;Currently, the VLAN id may be used without validation when
receive a VLAN configuration mailbox from VF. The length of
vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause
out-of-bounds memory access once the VLAN id is bigger than
or equal to VLAN_N_VID.&lt;/p&gt;
&lt;p&gt;Therefore, VLAN id needs to be checked to ensure it is within
the range of VLAN_N_VID.(CVE-2025-71112)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix string copying in parse_apply_sb_mount_options()&lt;/p&gt;
&lt;p&gt;strscpy_pad() can&amp;amp;apos;t be used to copy a non-NUL-term string into a NUL-term
string of possibly bigger size.  Commit 0efc5990bca5 (&amp;amp;quot;string.h: Introduce
memtostr() and memtostr_pad()&amp;amp;quot;) provides additional information in that
regard.  So if this happens, the following warning is observed:&lt;/p&gt;
&lt;p&gt;strnlen: detected buffer overflow: 65 byte read of buffer size 64
WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Modules linked in:
CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 __fortify_panic+0x1f/0x30 lib/s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: 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: hns3: add VLAN id validation before using&lt;/p&gt;
&lt;p&gt;Currently, the VLAN id may be used without validation when
receive a VLAN configuration mailbox from VF. The length of
vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause
out-of-bounds memory access once the VLAN id is bigger than
or equal to VLAN_N_VID.&lt;/p&gt;
&lt;p&gt;Therefore, VLAN id needs to be checked to ensure it is within
the range of VLAN_N_VID.(CVE-2025-71112)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix string copying in parse_apply_sb_mount_options()&lt;/p&gt;
&lt;p&gt;strscpy_pad() can&amp;amp;apos;t be used to copy a non-NUL-term string into a NUL-term
string of possibly bigger size.  Commit 0efc5990bca5 (&amp;amp;quot;string.h: Introduce
memtostr() and memtostr_pad()&amp;amp;quot;) provides additional information in that
regard.  So if this happens, the following warning is observed:&lt;/p&gt;
&lt;p&gt;strnlen: detected buffer overflow: 65 byte read of buffer size 64
WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Modules linked in:
CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 __fortify_panic+0x1f/0x30 lib/s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3704</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64025</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64025</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: fix verdict sk_data_ready racing with ktls rx sk_psock_strp_data_ready() already checks tls_sw_has_ctx_rx() and defers to psock-&amp;gt;saved_data_ready when a TLS RX context is present, avoiding a conflict with the TLS strparser&amp;#39;s ownership of the receive queue (commit e91de6afa81c, &amp;#34;bpf: Fix running sk_skb program types with ktls&amp;#34;). sk_psock_verdict_data_ready() has no equivalent guard.  When a socket is inserted into a sockmap (BPF_SK_SKB_VERDICT) before TLS RX is configured, tls_sw_strparser_arm() saves sk_psock_verdict_data_ready as rx_ctx-&amp;gt;saved_data_ready.  On data arrival:   tls_data_ready -&amp;gt; tls_strp_data_ready -&amp;gt; tls_rx_msg_ready     -&amp;gt; saved_data_ready() = sk_psock_verdict_data_ready()       -&amp;gt; tcp_read_skb() drains sk_receive_queue via __skb_unlink()          without calling tcp_eat_skb(), so copied_seq is not advanced. tls_strp_msg_load() then finds tcp_inq() &amp;gt;= full_len (stale), calls tcp_recv_skb() on the now-empty queue, hits WARN_ON_ONCE(!first), and returns with rx_ctx-&amp;gt;strp.anchor.frag_list pointing at a psock-owned (potentially freed) skb.  tls_decrypt_sg() subsequently walks that frag_list: use-after-free. Apply the same fix as sk_psock_strp_data_ready(): if a TLS RX context is present, call psock-&amp;gt;saved_data_ready (sock_def_readable) to wake recv() waiters and return immediately, leaving the receive queue untouched.  TLS retains sole ownership of the queue and decrypts the record n…&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: fix verdict sk_data_ready racing with ktls rx sk_psock_strp_data_ready() already checks tls_sw_has_ctx_rx() and defers to psock-&amp;gt;saved_data_ready when a TLS RX context is present, avoiding a conflict with the TLS strparser&amp;#39;s ownership of the receive queue (commit e91de6afa81c, &amp;#34;bpf: Fix running sk_skb program types with ktls&amp;#34;). sk_psock_verdict_data_ready() has no equivalent guard.  When a socket is inserted into a sockmap (BPF_SK_SKB_VERDICT) before TLS RX is configured, tls_sw_strparser_arm() saves sk_psock_verdict_data_ready as rx_ctx-&amp;gt;saved_data_ready.  On data arrival:   tls_data_ready -&amp;gt; tls_strp_data_ready -&amp;gt; tls_rx_msg_ready     -&amp;gt; saved_data_ready() = sk_psock_verdict_data_ready()       -&amp;gt; tcp_read_skb() drains sk_receive_queue via __skb_unlink()          without calling tcp_eat_skb(), so copied_seq is not advanced. tls_strp_msg_load() then finds tcp_inq() &amp;gt;= full_len (stale), calls tcp_recv_skb() on the now-empty queue, hits WARN_ON_ONCE(!first), and returns with rx_ctx-&amp;gt;strp.anchor.frag_list pointing at a psock-owned (potentially freed) skb.  tls_decrypt_sg() subsequently walks that frag_list: use-after-free. Apply the same fix as sk_psock_strp_data_ready(): if a TLS RX context is present, call psock-&amp;gt;saved_data_ready (sock_def_readable) to wake recv() waiters and return immediately, leaving the receive queue untouched.  TLS retains sole ownership of the queue and decrypts the record n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64025</guid>
    </item>
  </channel>
</rss>
