<?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 04:54:13 +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-53256</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53256</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-53256</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-3204 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3204</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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: rtw88: Use devm_kmemdup() in rtw_set_supported_band()&lt;/p&gt;
&lt;p&gt;Simplify the code by using device managed memory allocations.&lt;/p&gt;
&lt;p&gt;This also fixes a memory leak in rtw_register_hw(). The supported bands
were not freed in the error path.&lt;/p&gt;
&lt;p&gt;Copied from commit 145df52a8671 (&amp;amp;quot;wifi: rtw89: Convert
rtw89_core_set_supported_band to use devm_*&amp;amp;quot;).(CVE-2025-71273)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfrm: hold dev ref until after transport_finish NF_HOOK&lt;/p&gt;
&lt;p&gt;After async crypto completes, xfrm_input_resume() calls dev_put()
immediately on re-entry before the skb reaches transport_finish.
The skb-&amp;amp;gt;dev pointer is then used inside NF_HOOK and its okfn,
which can race with device teardown.&lt;/p&gt;
&lt;p&gt;Remove the dev_put from the async resumption entry and instead
drop the reference after the NF_HOOK call in transport_finish,
using a saved device pointer since NF_HOOK may consume the skb.
This covers NF_DROP, NF_QUEUE and NF_STOLEN paths that skip
the okfn.&lt;/p&gt;
&lt;p&gt;For non-transport exits (decaps, gro, drop) and secondary
async return points, release the reference inline when
async is set.(CVE-2026-31663)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: shadow stacks: proper error handling for mmap lock&lt;/p&gt;
&lt;p&gt;김영민 reports that shstk_pop_sigframe() doesn&amp;amp;apos;t check for errors from
mmap_read_lock_killable(), whic…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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: rtw88: Use devm_kmemdup() in rtw_set_supported_band()&lt;/p&gt;
&lt;p&gt;Simplify the code by using device managed memory allocations.&lt;/p&gt;
&lt;p&gt;This also fixes a memory leak in rtw_register_hw(). The supported bands
were not freed in the error path.&lt;/p&gt;
&lt;p&gt;Copied from commit 145df52a8671 (&amp;amp;quot;wifi: rtw89: Convert
rtw89_core_set_supported_band to use devm_*&amp;amp;quot;).(CVE-2025-71273)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfrm: hold dev ref until after transport_finish NF_HOOK&lt;/p&gt;
&lt;p&gt;After async crypto completes, xfrm_input_resume() calls dev_put()
immediately on re-entry before the skb reaches transport_finish.
The skb-&amp;amp;gt;dev pointer is then used inside NF_HOOK and its okfn,
which can race with device teardown.&lt;/p&gt;
&lt;p&gt;Remove the dev_put from the async resumption entry and instead
drop the reference after the NF_HOOK call in transport_finish,
using a saved device pointer since NF_HOOK may consume the skb.
This covers NF_DROP, NF_QUEUE and NF_STOLEN paths that skip
the okfn.&lt;/p&gt;
&lt;p&gt;For non-transport exits (decaps, gro, drop) and secondary
async return points, release the reference inline when
async is set.(CVE-2026-31663)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: shadow stacks: proper error handling for mmap lock&lt;/p&gt;
&lt;p&gt;김영민 reports that shstk_pop_sigframe() doesn&amp;amp;apos;t check for errors from
mmap_read_lock_killable(), whic…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3204</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-53256</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53256</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 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() rfcomm_get_sock_by_channel() scans rfcomm_sk_list under the list lock, but returns the selected listener after dropping that lock without taking a reference. rfcomm_connect_ind() then locks the listener, queues a child socket on it, and may notify it after unlocking it. The buggy scenario involves two paths, with each column showing the order within that path: rfcomm_connect_ind():            listener close:   1. Find parent in              1. close() enters      rfcomm_get_sock_by_channel()   rfcomm_sock_release().   2. Drop rfcomm_sk_list.lock    2. rfcomm_sock_shutdown()      without pinning parent.        closes the listener.   3. Call lock_sock(parent) and  3. rfcomm_sock_kill()      bt_accept_enqueue(parent,      unlinks and puts parent.      sk, true).   4. Read parent flags and may   4. parent can be freed.      call sk_state_change(). If close wins the race, parent can be freed before rfcomm_connect_ind() reaches lock_sock(), bt_accept_enqueue(), or the deferred-setup callback. Take a reference on the listener before leaving rfcomm_sk_list.lock. After lock_sock() succeeds, recheck that it is still in BT_LISTEN before queueing a child, cache the deferred-setup bit while the parent is locked, and drop the reference after the last parent use. KASAN reported a slab-use-after-free in lock_sock_nested() from rfcomm_connect_ind(), with the fre…&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 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() rfcomm_get_sock_by_channel() scans rfcomm_sk_list under the list lock, but returns the selected listener after dropping that lock without taking a reference. rfcomm_connect_ind() then locks the listener, queues a child socket on it, and may notify it after unlocking it. The buggy scenario involves two paths, with each column showing the order within that path: rfcomm_connect_ind():            listener close:   1. Find parent in              1. close() enters      rfcomm_get_sock_by_channel()   rfcomm_sock_release().   2. Drop rfcomm_sk_list.lock    2. rfcomm_sock_shutdown()      without pinning parent.        closes the listener.   3. Call lock_sock(parent) and  3. rfcomm_sock_kill()      bt_accept_enqueue(parent,      unlinks and puts parent.      sk, true).   4. Read parent flags and may   4. parent can be freed.      call sk_state_change(). If close wins the race, parent can be freed before rfcomm_connect_ind() reaches lock_sock(), bt_accept_enqueue(), or the deferred-setup callback. Take a reference on the listener before leaving rfcomm_sk_list.lock. After lock_sock() succeeds, recheck that it is still in BT_LISTEN before queueing a child, cache the deferred-setup bit while the parent is locked, and drop the reference after the last parent use. KASAN reported a slab-use-after-free in lock_sock_nested() from rfcomm_connect_ind(), with the fre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53256</guid>
    </item>
  </channel>
</rss>
