<?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 15:43:47 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:77689 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:77689</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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)
  * kernel: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use (CVE-2026-53360)
  * kernel: vsock/virtio: fix zerocopy completion for multi-skb sends (CVE-2026-53365)
  * kernel: NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)
  * kernel: vsock/virtio: bind uarg before filling zerocopy skb (CVE-2026-63970)
  * kernel: igc: set tx buffer type for SMD frames (CVE-2026-64035)
  * kernel: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (CVE-2026-64162)
  * kernel: vsock/vmci: fix UAF when peer resets connection during handshake (CVE-2026-64115)
  * kernel: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (CVE-2026-72317)
  * kernel: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (CVE-2026-74744)
  * kernel: nfsd: defer vfree of compound ops to fix rpc_status UAF (CVE-2026-89690)
  * kernel: nfsd: initialize copy-notify stateid before publishing it (CVE-2026-89669)
  * kernel: svcrdma: Reject inline replies that overflow the pull-up buffer (CVE-2026-89530)
  * kernel: nfsd: revoke copy-notify stateids before dropping their reference (CVE-2026-89663)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* &amp;#34;iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors&amp;#34; broke rx-vlan-offload on almalinux-9.7 [almalinux-9.8.z] (JIRA:AlmaLinux-169480…&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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)
  * kernel: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use (CVE-2026-53360)
  * kernel: vsock/virtio: fix zerocopy completion for multi-skb sends (CVE-2026-53365)
  * kernel: NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)
  * kernel: vsock/virtio: bind uarg before filling zerocopy skb (CVE-2026-63970)
  * kernel: igc: set tx buffer type for SMD frames (CVE-2026-64035)
  * kernel: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (CVE-2026-64162)
  * kernel: vsock/vmci: fix UAF when peer resets connection during handshake (CVE-2026-64115)
  * kernel: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (CVE-2026-72317)
  * kernel: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (CVE-2026-74744)
  * kernel: nfsd: defer vfree of compound ops to fix rpc_status UAF (CVE-2026-89690)
  * kernel: nfsd: initialize copy-notify stateid before publishing it (CVE-2026-89669)
  * kernel: svcrdma: Reject inline replies that overflow the pull-up buffer (CVE-2026-89530)
  * kernel: nfsd: revoke copy-notify stateids before dropping their reference (CVE-2026-89663)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* &amp;#34;iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors&amp;#34; broke rx-vlan-offload on almalinux-9.7 [almalinux-9.8.z] (JIRA:AlmaLinux-169480…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:77689</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-89663</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-89663</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-89663</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>OESA-2026-4357 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-4357</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;fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist&lt;/p&gt;
&lt;p&gt;Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.&lt;/p&gt;
&lt;p&gt;syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.&lt;/p&gt;
&lt;p&gt;Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;batman-adv: fix fragment reassembly length accounting&lt;/p&gt;
&lt;p&gt;batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.&lt;/p&gt;
&lt;p&gt;That accounting currently allows the accumulated fragment length to be
truncated during updates. As a result, malformed fragment chains can
bypass the intended validation and drive reassembly with inconsistent
length state, leading to a local denial of service.&lt;/p&gt;
&lt;p&gt;Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.&lt;/p&gt;
&lt;p&gt;T…&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;fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist&lt;/p&gt;
&lt;p&gt;Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.&lt;/p&gt;
&lt;p&gt;syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.&lt;/p&gt;
&lt;p&gt;Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;batman-adv: fix fragment reassembly length accounting&lt;/p&gt;
&lt;p&gt;batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.&lt;/p&gt;
&lt;p&gt;That accounting currently allows the accumulated fragment length to be
truncated during updates. As a result, malformed fragment chains can
bypass the intended validation and drive reassembly with inconsistent
length state, leading to a local denial of service.&lt;/p&gt;
&lt;p&gt;Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.&lt;/p&gt;
&lt;p&gt;T…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-4357</guid>
    </item>
    <item>
      <title>RLSA-2026:77689 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:77689</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: kernel, Rocky Linux:9: kernel-64k, Rocky Linux:9: kernel-64k-core, Rocky Linux:9: kernel-64k-debug, Rocky Linux:9: kernel-64k-debug-core, Rocky Linux:9: kernel-64k-debug-debuginfo, Rocky Linux:9: kernel-64k-debug-devel, Rocky Linux:9: kernel-64k-debug-devel-matched, Rocky Linux:9: kernel-64k-debuginfo, Rocky Linux:9: kernel-64k-debug-modules and 79 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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use (CVE-2026-53360)&lt;/p&gt;
&lt;p&gt;* kernel: vsock/virtio: fix zerocopy completion for multi-skb sends (CVE-2026-53365)&lt;/p&gt;
&lt;p&gt;* kernel: NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)&lt;/p&gt;
&lt;p&gt;* kernel: vsock/virtio: bind uarg before filling zerocopy skb (CVE-2026-63970)&lt;/p&gt;
&lt;p&gt;* kernel: igc: set tx buffer type for SMD frames (CVE-2026-64035)&lt;/p&gt;
&lt;p&gt;* kernel: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (CVE-2026-64162)&lt;/p&gt;
&lt;p&gt;* kernel: vsock/vmci: fix UAF when peer resets connection during handshake (CVE-2026-64115)&lt;/p&gt;
&lt;p&gt;* kernel: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (CVE-2026-72317)&lt;/p&gt;
&lt;p&gt;* kernel: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (CVE-2026-74744)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: defer vfree of compound ops to fix rpc_status UAF (CVE-2026-89690)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: initialize copy-notify stateid before publishing it (CVE-2026-89669)&lt;/p&gt;
&lt;p&gt;* kernel: svcrdma: Reject inline replies that overflow the pull-up buffer (CVE-2026-89530)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: revoke copy-notify stateids before dropping their reference (CVE-2026-89663)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* &amp;#34;iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors&amp;#34; broke rx-vlan-offload on rhel-9.7 [rhel-9.8.z] (JIRA:Rocky Linux-169480)&lt;/p&gt;
&lt;p&gt;* [GNR-D] missing interfaces…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: kernel, Rocky Linux:9: kernel-64k, Rocky Linux:9: kernel-64k-core, Rocky Linux:9: kernel-64k-debug, Rocky Linux:9: kernel-64k-debug-core, Rocky Linux:9: kernel-64k-debug-debuginfo, Rocky Linux:9: kernel-64k-debug-devel, Rocky Linux:9: kernel-64k-debug-devel-matched, Rocky Linux:9: kernel-64k-debuginfo, Rocky Linux:9: kernel-64k-debug-modules and 79 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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use (CVE-2026-53360)&lt;/p&gt;
&lt;p&gt;* kernel: vsock/virtio: fix zerocopy completion for multi-skb sends (CVE-2026-53365)&lt;/p&gt;
&lt;p&gt;* kernel: NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)&lt;/p&gt;
&lt;p&gt;* kernel: vsock/virtio: bind uarg before filling zerocopy skb (CVE-2026-63970)&lt;/p&gt;
&lt;p&gt;* kernel: igc: set tx buffer type for SMD frames (CVE-2026-64035)&lt;/p&gt;
&lt;p&gt;* kernel: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (CVE-2026-64162)&lt;/p&gt;
&lt;p&gt;* kernel: vsock/vmci: fix UAF when peer resets connection during handshake (CVE-2026-64115)&lt;/p&gt;
&lt;p&gt;* kernel: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (CVE-2026-72317)&lt;/p&gt;
&lt;p&gt;* kernel: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (CVE-2026-74744)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: defer vfree of compound ops to fix rpc_status UAF (CVE-2026-89690)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: initialize copy-notify stateid before publishing it (CVE-2026-89669)&lt;/p&gt;
&lt;p&gt;* kernel: svcrdma: Reject inline replies that overflow the pull-up buffer (CVE-2026-89530)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: revoke copy-notify stateids before dropping their reference (CVE-2026-89663)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* &amp;#34;iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors&amp;#34; broke rx-vlan-offload on rhel-9.7 [rhel-9.8.z] (JIRA:Rocky Linux-169480)&lt;/p&gt;
&lt;p&gt;* [GNR-D] missing interfaces…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:77689</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89663</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89663</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 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: revoke copy-notify stateids before dropping their reference Copy-notify stateids live in the s2s_cp_stateids IDR and on their parent stid&amp;#39;s sc_cp_list, pinned by a single membership reference. _free_cpntf_state_locked() only unlinks an entry once its refcount reaches zero, so any revoke path that runs while a concurrent find_cpntf_state()/manage_cpntf_state() holder has elevated cs_count drops the reference without unlinking, leaving the entry discoverable with its membership reference already consumed. A second revoke or a laundromat tick then frees it while the reader still holds the pointer -- a KASAN-detectable use-after-free at the reader&amp;#39;s nfs4_put_cpntf_state(). This affected all three revoke paths:   - The parent-stid drain (nfs4_free_cpntf_statelist()) repeatedly called     _free_cpntf_state_locked() on the first list entry; a holder that had     bumped cs_count made it return early, so the next iteration     re-decremented and burned the holder&amp;#39;s reference.   - OFFLOAD_CANCEL (manage_cpntf_state()) and laundromat expiry likewise     used _free_cpntf_state_locked() and could drop 2-&amp;gt;1 without unlinking. Add revoke_cpntf_state_locked(), which unhashes the entry from the IDR and sc_cp_list first (deferring the final free to any holder), and use it from all three revoke paths. The drain now walks with list_for_each_entry_safe() and revokes each entry unconditionally, so it terminates in one pass…&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 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: revoke copy-notify stateids before dropping their reference Copy-notify stateids live in the s2s_cp_stateids IDR and on their parent stid&amp;#39;s sc_cp_list, pinned by a single membership reference. _free_cpntf_state_locked() only unlinks an entry once its refcount reaches zero, so any revoke path that runs while a concurrent find_cpntf_state()/manage_cpntf_state() holder has elevated cs_count drops the reference without unlinking, leaving the entry discoverable with its membership reference already consumed. A second revoke or a laundromat tick then frees it while the reader still holds the pointer -- a KASAN-detectable use-after-free at the reader&amp;#39;s nfs4_put_cpntf_state(). This affected all three revoke paths:   - The parent-stid drain (nfs4_free_cpntf_statelist()) repeatedly called     _free_cpntf_state_locked() on the first list entry; a holder that had     bumped cs_count made it return early, so the next iteration     re-decremented and burned the holder&amp;#39;s reference.   - OFFLOAD_CANCEL (manage_cpntf_state()) and laundromat expiry likewise     used _free_cpntf_state_locked() and could drop 2-&amp;gt;1 without unlinking. Add revoke_cpntf_state_locked(), which unhashes the entry from the IDR and sc_cp_list first (deferring the final free to any holder), and use it from all three revoke paths. The drain now walks with list_for_each_entry_safe() and revokes each entry unconditionally, so it terminates in one pass…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89663</guid>
    </item>
  </channel>
</rss>
