<?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:30:10 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:19568 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:19568</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 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: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (CVE-2025-39766)
  * kernel: scsi: qla2xxx: Fix improper freeing of purex item (CVE-2025-68741)
  * kernel: libceph: make decode_pool() more resilient against corrupted osdmaps (CVE-2025-71116)
  * kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() (CVE-2026-22984)
  * kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (CVE-2026-22990)
  * kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state (CVE-2026-23136)
  * kernel: net/sched: cls_u32: use skb_header_pointer_careful() (CVE-2026-23204)
  * kernel: Linux kernel: Use-after-free in traffic control (act_ct) may lead to denial of service or privilege escalation (CVE-2026-23270)
  * kernel: Linux kernel KVM: Privilege escalation or denial of service due to improper shadow page table entry handling (CVE-2026-23401)
  * kernel: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (CVE-2026-31402)
  * kernel: can: raw: fix ro-&amp;gt;uniq use-after-free in raw_rcv() (CVE-2026-31532)
  * kernel: usbip: validate number_of_packets in usbip_pack_ret_submit() (CVE-2026-31607)
  * kernel: md/bitmap: fix GPF in write_page caused by resize race (CVE-2026-43163)
  * kernel: RDMA/umem: Fix double dma_buf_unpin in failure path (CVE-2026-43128)
  * kernel: &amp;#34;Dirty Frag&amp;#34; i…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 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: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (CVE-2025-39766)
  * kernel: scsi: qla2xxx: Fix improper freeing of purex item (CVE-2025-68741)
  * kernel: libceph: make decode_pool() more resilient against corrupted osdmaps (CVE-2025-71116)
  * kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() (CVE-2026-22984)
  * kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (CVE-2026-22990)
  * kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state (CVE-2026-23136)
  * kernel: net/sched: cls_u32: use skb_header_pointer_careful() (CVE-2026-23204)
  * kernel: Linux kernel: Use-after-free in traffic control (act_ct) may lead to denial of service or privilege escalation (CVE-2026-23270)
  * kernel: Linux kernel KVM: Privilege escalation or denial of service due to improper shadow page table entry handling (CVE-2026-23401)
  * kernel: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (CVE-2026-31402)
  * kernel: can: raw: fix ro-&amp;gt;uniq use-after-free in raw_rcv() (CVE-2026-31532)
  * kernel: usbip: validate number_of_packets in usbip_pack_ret_submit() (CVE-2026-31607)
  * kernel: md/bitmap: fix GPF in write_page caused by resize race (CVE-2026-43163)
  * kernel: RDMA/umem: Fix double dma_buf_unpin in failure path (CVE-2026-43128)
  * kernel: &amp;#34;Dirty Frag&amp;#34; i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:19568</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-31607</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-31607</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-31607</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0526 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0526</link>
      <description>certfr-2026-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0526</guid>
    </item>
    <item>
      <title>OESA-2026-2674 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2674</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;btrfs: qgroup: fix race between quota disable and quota rescan ioctl&lt;/p&gt;
&lt;p&gt;There&amp;amp;apos;s a race between a task disabling quotas and another running the
rescan ioctl that can result in a use-after-free of qgroup records from
the fs_info-&amp;amp;gt;qgroup_tree rbtree.&lt;/p&gt;
&lt;p&gt;This happens as follows:&lt;/p&gt;
&lt;p&gt;1) Task A enters btrfs_ioctl_quota_rescan() -&amp;amp;gt; btrfs_qgroup_rescan();&lt;/p&gt;
&lt;p&gt;2) Task B enters btrfs_quota_disable() and calls
   btrfs_qgroup_wait_for_completion(), which does nothing because at that
   point fs_info-&amp;amp;gt;qgroup_rescan_running is false (it wasn&amp;amp;apos;t set yet by
   task A);&lt;/p&gt;
&lt;p&gt;3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups
   from fs_info-&amp;amp;gt;qgroup_tree without taking the lock fs_info-&amp;amp;gt;qgroup_lock;&lt;/p&gt;
&lt;p&gt;4) Task A enters qgroup_rescan_zero_tracking() which starts iterating
   the fs_info-&amp;amp;gt;qgroup_tree tree while holding fs_info-&amp;amp;gt;qgroup_lock,
   but task B is freeing qgroup records from that tree without holding
   the lock, resulting in a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by taking fs_info-&amp;amp;gt;qgroup_lock at btrfs_free_qgroup_config().
Also at btrfs_qgroup_rescan() don&amp;amp;apos;t start the rescan worker if quotas
were already disabled.(CVE-2025-39759)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: wilc1000: avoid buffer overflow in WID string configuration&lt;/p&gt;
&lt;p&gt;Fix the following copy overflow warning identi…&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;btrfs: qgroup: fix race between quota disable and quota rescan ioctl&lt;/p&gt;
&lt;p&gt;There&amp;amp;apos;s a race between a task disabling quotas and another running the
rescan ioctl that can result in a use-after-free of qgroup records from
the fs_info-&amp;amp;gt;qgroup_tree rbtree.&lt;/p&gt;
&lt;p&gt;This happens as follows:&lt;/p&gt;
&lt;p&gt;1) Task A enters btrfs_ioctl_quota_rescan() -&amp;amp;gt; btrfs_qgroup_rescan();&lt;/p&gt;
&lt;p&gt;2) Task B enters btrfs_quota_disable() and calls
   btrfs_qgroup_wait_for_completion(), which does nothing because at that
   point fs_info-&amp;amp;gt;qgroup_rescan_running is false (it wasn&amp;amp;apos;t set yet by
   task A);&lt;/p&gt;
&lt;p&gt;3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups
   from fs_info-&amp;amp;gt;qgroup_tree without taking the lock fs_info-&amp;amp;gt;qgroup_lock;&lt;/p&gt;
&lt;p&gt;4) Task A enters qgroup_rescan_zero_tracking() which starts iterating
   the fs_info-&amp;amp;gt;qgroup_tree tree while holding fs_info-&amp;amp;gt;qgroup_lock,
   but task B is freeing qgroup records from that tree without holding
   the lock, resulting in a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by taking fs_info-&amp;amp;gt;qgroup_lock at btrfs_free_qgroup_config().
Also at btrfs_qgroup_rescan() don&amp;amp;apos;t start the rescan worker if quotas
were already disabled.(CVE-2025-39759)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: wilc1000: avoid buffer overflow in WID string configuration&lt;/p&gt;
&lt;p&gt;Fix the following copy overflow warning identi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2674</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31607</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31607</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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usbip: validate number_of_packets in usbip_pack_ret_submit() When a USB/IP client receives a RET_SUBMIT response, usbip_pack_ret_submit() unconditionally overwrites urb-&amp;gt;number_of_packets from the network PDU. This value is subsequently used as the loop bound in usbip_recv_iso() and usbip_pad_iso() to iterate over urb-&amp;gt;iso_frame_desc[], a flexible array whose size was fixed at URB allocation time based on the *original* number_of_packets from the CMD_SUBMIT. A malicious USB/IP server can set number_of_packets in the response to a value larger than what was originally submitted, causing a heap out-of-bounds write when usbip_recv_iso() writes to urb-&amp;gt;iso_frame_desc[i] beyond the allocated region. KASAN confirmed this with kernel 7.0.0-rc5:   BUG: KASAN: slab-out-of-bounds in usbip_recv_iso+0x46a/0x640   Write of size 4 at addr ffff888106351d40 by task vhci_rx/69   The buggy address is located 0 bytes to the right of    allocated 320-byte region [ffff888106351c00, ffff888106351d40) The server side (stub_rx.c) and gadget side (vudc_rx.c) already validate number_of_packets in the CMD_SUBMIT path since commits c6688ef9f297 (&amp;#34;usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input&amp;#34;) and b78d830f0049 (&amp;#34;usbip: fix vudc_rx: harden CMD_SUBMIT path to handle malicious input&amp;#34;). The server side validates against USBIP_MAX_ISO_PACKETS because no URB exists yet at that point. On the client side we have the orig…&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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usbip: validate number_of_packets in usbip_pack_ret_submit() When a USB/IP client receives a RET_SUBMIT response, usbip_pack_ret_submit() unconditionally overwrites urb-&amp;gt;number_of_packets from the network PDU. This value is subsequently used as the loop bound in usbip_recv_iso() and usbip_pad_iso() to iterate over urb-&amp;gt;iso_frame_desc[], a flexible array whose size was fixed at URB allocation time based on the *original* number_of_packets from the CMD_SUBMIT. A malicious USB/IP server can set number_of_packets in the response to a value larger than what was originally submitted, causing a heap out-of-bounds write when usbip_recv_iso() writes to urb-&amp;gt;iso_frame_desc[i] beyond the allocated region. KASAN confirmed this with kernel 7.0.0-rc5:   BUG: KASAN: slab-out-of-bounds in usbip_recv_iso+0x46a/0x640   Write of size 4 at addr ffff888106351d40 by task vhci_rx/69   The buggy address is located 0 bytes to the right of    allocated 320-byte region [ffff888106351c00, ffff888106351d40) The server side (stub_rx.c) and gadget side (vudc_rx.c) already validate number_of_packets in the CMD_SUBMIT path since commits c6688ef9f297 (&amp;#34;usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input&amp;#34;) and b78d830f0049 (&amp;#34;usbip: fix vudc_rx: harden CMD_SUBMIT path to handle malicious input&amp;#34;). The server side validates against USBIP_MAX_ISO_PACKETS because no URB exists yet at that point. On the client side we have the orig…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31607</guid>
    </item>
  </channel>
</rss>
