<?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 00:44:28 +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-53357</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53357</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-53357</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>OESA-2026-2930 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2930</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;wifi: mac80211: check tdls flag in ieee80211_tdls_oper&lt;/p&gt;
&lt;p&gt;When NL80211_TDLS_ENABLE_LINK is called, the code only checks if the
station exists but not whether it is actually a TDLS station. This
allows the operation to proceed for non-TDLS stations, causing
unintended side effects like modifying channel context and HT
protection before failing.&lt;/p&gt;
&lt;p&gt;Add a check for sta-&amp;amp;gt;sta.tdls early in the ENABLE_LINK case, before
any side effects occur, to ensure the operation is only allowed for
actual TDLS peers.(CVE-2026-43052)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmfmac: validate bsscfg indices in IF events&lt;/p&gt;
&lt;p&gt;brcmf_fweh_handle_if_event() validates the firmware-provided interface
index before it touches drvr-&amp;amp;gt;iflist[], but it still uses the raw
bsscfgidx field as an array index without a matching range check.&lt;/p&gt;
&lt;p&gt;Reject IF events whose bsscfg index does not fit in drvr-&amp;amp;gt;iflist[]
before indexing the interface array.&lt;/p&gt;
&lt;p&gt;[add missing wifi prefix](CVE-2026-43110)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: roccat: fix use-after-free in roccat_report_event&lt;/p&gt;
&lt;p&gt;roccat_report_event() iterates over the device-&amp;amp;gt;readers list without
holding the readers_lock. This allows a concurrent roccat_release() to
remove and free a reader while it&amp;amp;apos;s still being accessed, leading to a
use-after-f…&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;wifi: mac80211: check tdls flag in ieee80211_tdls_oper&lt;/p&gt;
&lt;p&gt;When NL80211_TDLS_ENABLE_LINK is called, the code only checks if the
station exists but not whether it is actually a TDLS station. This
allows the operation to proceed for non-TDLS stations, causing
unintended side effects like modifying channel context and HT
protection before failing.&lt;/p&gt;
&lt;p&gt;Add a check for sta-&amp;amp;gt;sta.tdls early in the ENABLE_LINK case, before
any side effects occur, to ensure the operation is only allowed for
actual TDLS peers.(CVE-2026-43052)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmfmac: validate bsscfg indices in IF events&lt;/p&gt;
&lt;p&gt;brcmf_fweh_handle_if_event() validates the firmware-provided interface
index before it touches drvr-&amp;amp;gt;iflist[], but it still uses the raw
bsscfgidx field as an array index without a matching range check.&lt;/p&gt;
&lt;p&gt;Reject IF events whose bsscfg index does not fit in drvr-&amp;amp;gt;iflist[]
before indexing the interface array.&lt;/p&gt;
&lt;p&gt;[add missing wifi prefix](CVE-2026-43110)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: roccat: fix use-after-free in roccat_report_event&lt;/p&gt;
&lt;p&gt;roccat_report_event() iterates over the device-&amp;amp;gt;readers list without
holding the readers_lock. This allows a concurrent roccat_release() to
remove and free a reader while it&amp;amp;apos;s still being accessed, leading to a
use-after-f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2930</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53357</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53357</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 202 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close.  A concurrent HCI disconnect drives hci_rx_work -&amp;gt; l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both:   BUG: KASAN: slab-use-after-free in l2cap_sock_kill     l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close   Freed by: l2cap_conn_del -&amp;gt; l2cap_sock_close_cb -&amp;gt; l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 (&amp;#34;Bluetooth: serialize accept_q access&amp;#34;) serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs l2cap_sock_t…&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 202 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close.  A concurrent HCI disconnect drives hci_rx_work -&amp;gt; l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both:   BUG: KASAN: slab-use-after-free in l2cap_sock_kill     l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close   Freed by: l2cap_conn_del -&amp;gt; l2cap_sock_close_cb -&amp;gt; l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 (&amp;#34;Bluetooth: serialize accept_q access&amp;#34;) serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs l2cap_sock_t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53357</guid>
    </item>
  </channel>
</rss>
