<?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:08 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:76738 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:76738</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&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: netfilter: nf_conncount: increase the connection clean up limit to 64 (CVE-2026-45860)
  * kernel: RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send (CVE-2026-45856)
  * kernel: Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths (CVE-2026-46275)
  * kernel: crypto: af_alg - Cap AEAD AD length to 0x80000000 (CVE-2026-52972)
  * kernel: ipvs: clear the svc scheduler ptr early on edit (CVE-2026-53270)
  * kernel: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() (CVE-2026-53357)
  * kernel: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (CVE-2026-63829)
  * kernel: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path (CVE-2026-63794)
  * kernel: ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() (CVE-2026-63924)
  * kernel: ipv6: exthdrs: refresh nh after handling HAO option (CVE-2026-63922)
  * kernel: ipv6: validate extension header length before copying to cmsg (CVE-2026-63920)
  * kernel: tcp: fix stale per-CPU tcp_tw_isn leak enabling ISN prediction (CVE-2026-64024)
  * kernel: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname (CVE-2026-63918)
  * kernel: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (CVE-2026-63984)
  * kernel: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (CVE-2026-63992)
  * kernel:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&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: netfilter: nf_conncount: increase the connection clean up limit to 64 (CVE-2026-45860)
  * kernel: RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send (CVE-2026-45856)
  * kernel: Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths (CVE-2026-46275)
  * kernel: crypto: af_alg - Cap AEAD AD length to 0x80000000 (CVE-2026-52972)
  * kernel: ipvs: clear the svc scheduler ptr early on edit (CVE-2026-53270)
  * kernel: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() (CVE-2026-53357)
  * kernel: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (CVE-2026-63829)
  * kernel: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path (CVE-2026-63794)
  * kernel: ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() (CVE-2026-63924)
  * kernel: ipv6: exthdrs: refresh nh after handling HAO option (CVE-2026-63922)
  * kernel: ipv6: validate extension header length before copying to cmsg (CVE-2026-63920)
  * kernel: tcp: fix stale per-CPU tcp_tw_isn leak enabling ISN prediction (CVE-2026-64024)
  * kernel: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname (CVE-2026-63918)
  * kernel: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (CVE-2026-63984)
  * kernel: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (CVE-2026-63992)
  * kernel:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:76738</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-63920</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-63920</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-63920</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-3532 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3532</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;uaccess: fix integer overflow on access_ok()&lt;/p&gt;
&lt;p&gt;Three architectures check the end of a user access against the
address limit without taking a possible overflow into account.
Passing a negative length or another overflow in here returns
success when it should not.&lt;/p&gt;
&lt;p&gt;Use the most common correct implementation here, which optimizes
for a constant &amp;amp;apos;size&amp;amp;apos; argument, and turns the common case into a
single comparison.(CVE-2022-49289)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;parisc: Fix double SIGFPE crash&lt;/p&gt;
&lt;p&gt;Camm noticed that on parisc a SIGFPE exception will crash an application with
a second SIGFPE in the signal handler.  Dave analyzed it, and it happens
because glibc uses a double-word floating-point store to atomically update
function descriptors. As a result of lazy binding, we hit a floating-point
store in fpe_func almost immediately.&lt;/p&gt;
&lt;p&gt;When the T bit is set, an assist exception trap occurs when when the
co-processor encounters *any* floating-point instruction except for a double
store of register %fr0.  The latter cancels all pending traps.  Let&amp;amp;apos;s fix this
by clearing the Trap (T) bit in the FP status register before returning to the
signal handler in userspace.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with this test program:&lt;/p&gt;
&lt;p&gt;root@parisc:~# cat fpe.c&lt;/p&gt;
&lt;p&gt;static void fpe_func(int sig, siginfo_t *i, void *v) {…&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;uaccess: fix integer overflow on access_ok()&lt;/p&gt;
&lt;p&gt;Three architectures check the end of a user access against the
address limit without taking a possible overflow into account.
Passing a negative length or another overflow in here returns
success when it should not.&lt;/p&gt;
&lt;p&gt;Use the most common correct implementation here, which optimizes
for a constant &amp;amp;apos;size&amp;amp;apos; argument, and turns the common case into a
single comparison.(CVE-2022-49289)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;parisc: Fix double SIGFPE crash&lt;/p&gt;
&lt;p&gt;Camm noticed that on parisc a SIGFPE exception will crash an application with
a second SIGFPE in the signal handler.  Dave analyzed it, and it happens
because glibc uses a double-word floating-point store to atomically update
function descriptors. As a result of lazy binding, we hit a floating-point
store in fpe_func almost immediately.&lt;/p&gt;
&lt;p&gt;When the T bit is set, an assist exception trap occurs when when the
co-processor encounters *any* floating-point instruction except for a double
store of register %fr0.  The latter cancels all pending traps.  Let&amp;amp;apos;s fix this
by clearing the Trap (T) bit in the FP status register before returning to the
signal handler in userspace.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with this test program:&lt;/p&gt;
&lt;p&gt;root@parisc:~# cat fpe.c&lt;/p&gt;
&lt;p&gt;static void fpe_func(int sig, siginfo_t *i, void *v) {…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3532</guid>
    </item>
    <item>
      <title>RLSA-2026:82806 — Important: kernel-rt security update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:82806</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt, Rocky Linux:8: kernel-rt-core, Rocky Linux:8: kernel-rt-debug, Rocky Linux:8: kernel-rt-debug-core, Rocky Linux:8: kernel-rt-debug-debuginfo, Rocky Linux:8: kernel-rt-debug-devel, Rocky Linux:8: kernel-rt-debuginfo, Rocky Linux:8: kernel-rt-debuginfo-common-x86_64, Rocky Linux:8: kernel-rt-debug-kvm, Rocky Linux:8: kernel-rt-debug-modules and 5 more&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: openvswitch: defer tunnel netdev_put to RCU release (CVE-2026-31678)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: validate extension header length before copying to cmsg (CVE-2026-63920)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: set new_stream to NULL after release (CVE-2026-68236)&lt;/p&gt;
&lt;p&gt;* kernel: drm/dp/mst: fix buffer overflows in sideband chunk accumulation (CVE-2026-68278)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: mac80211: defer link RX stats percpu free to RCU (CVE-2026-68409)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vce: fix integer overflow in image size (CVE-2026-68108)&lt;/p&gt;
&lt;p&gt;* kernel: drm/vmwgfx: use check_add_overflow for shader size+offset bound (CVE-2026-80887)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdkfd: Add TLB flush after MES queue eviction/suspension (CVE-2026-89811)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt, Rocky Linux:8: kernel-rt-core, Rocky Linux:8: kernel-rt-debug, Rocky Linux:8: kernel-rt-debug-core, Rocky Linux:8: kernel-rt-debug-debuginfo, Rocky Linux:8: kernel-rt-debug-devel, Rocky Linux:8: kernel-rt-debuginfo, Rocky Linux:8: kernel-rt-debuginfo-common-x86_64, Rocky Linux:8: kernel-rt-debug-kvm, Rocky Linux:8: kernel-rt-debug-modules and 5 more&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: openvswitch: defer tunnel netdev_put to RCU release (CVE-2026-31678)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: validate extension header length before copying to cmsg (CVE-2026-63920)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amd/display: set new_stream to NULL after release (CVE-2026-68236)&lt;/p&gt;
&lt;p&gt;* kernel: drm/dp/mst: fix buffer overflows in sideband chunk accumulation (CVE-2026-68278)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: mac80211: defer link RX stats percpu free to RCU (CVE-2026-68409)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdgpu/vce: fix integer overflow in image size (CVE-2026-68108)&lt;/p&gt;
&lt;p&gt;* kernel: drm/vmwgfx: use check_add_overflow for shader size+offset bound (CVE-2026-80887)&lt;/p&gt;
&lt;p&gt;* kernel: drm/amdkfd: Add TLB flush after MES queue eviction/suspension (CVE-2026-89811)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:82806</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63920</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63920</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: ipv6: validate extension header length before copying to cmsg ip6_datagram_recv_specific_ctl() builds IPV6_{HOPOPTS,DSTOPTS,RTHDR} cmsgs (and their IPV6_2292* legacy counterparts) by trusting the on-wire hdrlen byte (ptr[1]) when computing the put_cmsg() length. The length was validated only at parse time (ipv6_parse_hopopts(), etc.).  An nftables payload-write expression can rewrite hdrlen after parsing and before the skb reaches recvmsg; the write itself is in-bounds but put_cmsg() then reads up to ((hdrlen+1) &amp;lt;&amp;lt; 3) = 2040 bytes from an 8-byte header.  nftables is reachable from an unprivileged user namespace, so this is an unprivileged slab-out-of-bounds read:   BUG: KASAN: slab-out-of-bounds in put_cmsg+0x3ac/0x540    put_cmsg+0x3ac/0x540    udpv6_recvmsg+0xca0/0x1250    sock_recvmsg+0xdf/0x190    ____sys_recvmsg+0x1b1/0x620 Add ipv6_get_exthdr_len() which validates that at least two bytes are accessible before reading the hdrlen field, then checks the computed length against skb_tail_pointer(skb), returning 0 on failure.  Extension headers are kept in the linear skb area by pskb_may_pull() during input, so skb_tail_pointer() is the correct bound. Use ipv6_get_exthdr_len() at all non-AH call sites: the five standalone cmsg blocks (HbH, 2292HbH, 2292DSTOPTS x2, 2292RTHDR) and the three standard cases in the extension-header walk loop (DSTOPTS, ROUTING, default).  AH retains an inline bounds check because…&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: ipv6: validate extension header length before copying to cmsg ip6_datagram_recv_specific_ctl() builds IPV6_{HOPOPTS,DSTOPTS,RTHDR} cmsgs (and their IPV6_2292* legacy counterparts) by trusting the on-wire hdrlen byte (ptr[1]) when computing the put_cmsg() length. The length was validated only at parse time (ipv6_parse_hopopts(), etc.).  An nftables payload-write expression can rewrite hdrlen after parsing and before the skb reaches recvmsg; the write itself is in-bounds but put_cmsg() then reads up to ((hdrlen+1) &amp;lt;&amp;lt; 3) = 2040 bytes from an 8-byte header.  nftables is reachable from an unprivileged user namespace, so this is an unprivileged slab-out-of-bounds read:   BUG: KASAN: slab-out-of-bounds in put_cmsg+0x3ac/0x540    put_cmsg+0x3ac/0x540    udpv6_recvmsg+0xca0/0x1250    sock_recvmsg+0xdf/0x190    ____sys_recvmsg+0x1b1/0x620 Add ipv6_get_exthdr_len() which validates that at least two bytes are accessible before reading the hdrlen field, then checks the computed length against skb_tail_pointer(skb), returning 0 on failure.  Extension headers are kept in the linear skb area by pskb_may_pull() during input, so skb_tail_pointer() is the correct bound. Use ipv6_get_exthdr_len() at all non-AH call sites: the five standalone cmsg blocks (HbH, 2292HbH, 2292DSTOPTS x2, 2292RTHDR) and the three standard cases in the extension-header walk loop (DSTOPTS, ROUTING, default).  AH retains an inline bounds check because…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63920</guid>
    </item>
  </channel>
</rss>
