<?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:10:20 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:65334 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:65334</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: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)
  * kernel: Bluetooth: SMP: force responder MITM requirements before building the pairing response (CVE-2026-43334)
  * kernel: Bluetooth: virtio_bt: clamp rx length before skb_put (CVE-2026-46123)
  * kernel: Bluetooth: serialize accept_q access (CVE-2026-52918)
  * kernel: net: pull headers in qdisc_pkt_len_segs_init() (CVE-2026-53091)
  * kernel: Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (CVE-2026-53072)
  * kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)
  * kernel: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() (CVE-2026-53256)
  * kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)
  * kernel: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend (CVE-2026-53209)
  * kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers (CVE-2026-53254)
  * kernel: vfio/pci: Clean up DMABUFs before disabling function (CVE-2026-53322)
  * kernel: Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp (CVE-2026-63975)
  * kernel: security/keys: fix missed RCU read section on lookup (CVE-2026-64015)
  * kernel: Bluetooth: HIDP: fix missing length checks in hidp_input_report() (CVE-2026-63947)
  * kernel: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sy…&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: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)
  * kernel: Bluetooth: SMP: force responder MITM requirements before building the pairing response (CVE-2026-43334)
  * kernel: Bluetooth: virtio_bt: clamp rx length before skb_put (CVE-2026-46123)
  * kernel: Bluetooth: serialize accept_q access (CVE-2026-52918)
  * kernel: net: pull headers in qdisc_pkt_len_segs_init() (CVE-2026-53091)
  * kernel: Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (CVE-2026-53072)
  * kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)
  * kernel: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() (CVE-2026-53256)
  * kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)
  * kernel: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend (CVE-2026-53209)
  * kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers (CVE-2026-53254)
  * kernel: vfio/pci: Clean up DMABUFs before disabling function (CVE-2026-53322)
  * kernel: Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp (CVE-2026-63975)
  * kernel: security/keys: fix missed RCU read section on lookup (CVE-2026-64015)
  * kernel: Bluetooth: HIDP: fix missing length checks in hidp_input_report() (CVE-2026-63947)
  * kernel: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:65334</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-46123</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-46123</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-46123</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0731 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0731</link>
      <description>certfr-2026-avi-0731</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0731</guid>
    </item>
    <item>
      <title>RLSA-2026:65334 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:65334</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel-debuginfo, Rocky Linux:10: kernel-rt-core, Rocky Linux:10: kernel-debug, Rocky Linux:10: python3-perf-debuginfo, Rocky Linux:10: kernel-rt-debug-debuginfo, Rocky Linux:10: kernel-tools-libs-devel, Rocky Linux:10: kernel-debug-devel, Rocky Linux:10: kernel-rt-modules, Rocky Linux:10: kernel-rt-debug-core, Rocky Linux:10: kernel-modules-extra-matched and 80 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: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: SMP: force responder MITM requirements before building the pairing response (CVE-2026-43334)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: virtio_bt: clamp rx length before skb_put (CVE-2026-46123)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: serialize accept_q access (CVE-2026-52918)&lt;/p&gt;
&lt;p&gt;* kernel: net: pull headers in qdisc_pkt_len_segs_init() (CVE-2026-53091)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (CVE-2026-53072)&lt;/p&gt;
&lt;p&gt;* kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() (CVE-2026-53256)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend (CVE-2026-53209)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers (CVE-2026-53254)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: Clean up DMABUFs before disabling function (CVE-2026-53322)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp (CVE-2026-63975)&lt;/p&gt;
&lt;p&gt;* kernel: security/keys: fix missed RCU read section on lookup (CVE-2026-64015)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: HIDP: fix missing length checks in hidp_input_report() (CVE-2026-63947)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync (CVE-2026-63944)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel-debuginfo, Rocky Linux:10: kernel-rt-core, Rocky Linux:10: kernel-debug, Rocky Linux:10: python3-perf-debuginfo, Rocky Linux:10: kernel-rt-debug-debuginfo, Rocky Linux:10: kernel-tools-libs-devel, Rocky Linux:10: kernel-debug-devel, Rocky Linux:10: kernel-rt-modules, Rocky Linux:10: kernel-rt-debug-core, Rocky Linux:10: kernel-modules-extra-matched and 80 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: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: SMP: force responder MITM requirements before building the pairing response (CVE-2026-43334)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: virtio_bt: clamp rx length before skb_put (CVE-2026-46123)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: serialize accept_q access (CVE-2026-52918)&lt;/p&gt;
&lt;p&gt;* kernel: net: pull headers in qdisc_pkt_len_segs_init() (CVE-2026-53091)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (CVE-2026-53072)&lt;/p&gt;
&lt;p&gt;* kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() (CVE-2026-53256)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend (CVE-2026-53209)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers (CVE-2026-53254)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: Clean up DMABUFs before disabling function (CVE-2026-53322)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp (CVE-2026-63975)&lt;/p&gt;
&lt;p&gt;* kernel: security/keys: fix missed RCU read section on lookup (CVE-2026-64015)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: HIDP: fix missing length checks in hidp_input_report() (CVE-2026-63947)&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync (CVE-2026-63944)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:65334</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46123</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46123</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 201 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: clamp rx length before skb_put virtbt_rx_work() calls skb_put(skb, len) where len comes directly from virtqueue_get_buf() with no validation against the buffer we posted to the device. The RX skb is allocated in virtbt_add_inbuf() and exposed to virtio as exactly 1000 bytes via sg_init_one(). Checking len against skb_tailroom(skb) is not sufficient because alloc_skb() can leave more tailroom than the 1000 bytes actually handed to the device. A malicious or buggy backend can therefore report used.len between 1001 and skb_tailroom(skb), causing skb_put() to include uninitialized kernel heap bytes that were never written by the device. The same path also accepts len == 0, in which case skb_put(skb, 0) leaves the skb empty but virtbt_rx_handle() still reads the pkt_type byte from skb-&amp;gt;data, consuming uninitialized memory. Define VIRTBT_RX_BUF_SIZE once and reuse it in alloc_skb() and sg_init_one(), and gate virtbt_rx_work() on that same constant so the bound checked matches the buffer actually exposed to the device. Reject used.len == 0 in the same gate so an empty completion can no longer reach virtbt_rx_handle(). Use bt_dev_err_ratelimited() because the length value comes from an untrusted backend that can otherwise flood the kernel log. Same class of bug as commit c04db81cd028 (&amp;#34;net/9p: Fix buffer overflow in USB transport layer&amp;#34;), which hardened the USB 9p transport against unchecked de…&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 201 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: virtio_bt: clamp rx length before skb_put virtbt_rx_work() calls skb_put(skb, len) where len comes directly from virtqueue_get_buf() with no validation against the buffer we posted to the device. The RX skb is allocated in virtbt_add_inbuf() and exposed to virtio as exactly 1000 bytes via sg_init_one(). Checking len against skb_tailroom(skb) is not sufficient because alloc_skb() can leave more tailroom than the 1000 bytes actually handed to the device. A malicious or buggy backend can therefore report used.len between 1001 and skb_tailroom(skb), causing skb_put() to include uninitialized kernel heap bytes that were never written by the device. The same path also accepts len == 0, in which case skb_put(skb, 0) leaves the skb empty but virtbt_rx_handle() still reads the pkt_type byte from skb-&amp;gt;data, consuming uninitialized memory. Define VIRTBT_RX_BUF_SIZE once and reuse it in alloc_skb() and sg_init_one(), and gate virtbt_rx_work() on that same constant so the bound checked matches the buffer actually exposed to the device. Reject used.len == 0 in the same gate so an empty completion can no longer reach virtbt_rx_handle(). Use bt_dev_err_ratelimited() because the length value comes from an untrusted backend that can otherwise flood the kernel log. Same class of bug as commit c04db81cd028 (&amp;#34;net/9p: Fix buffer overflow in USB transport layer&amp;#34;), which hardened the USB 9p transport against unchecked de…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46123</guid>
    </item>
  </channel>
</rss>
