<?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://vulnerability.circl.lu</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>Wed, 30 Sep 2026 06:43:50 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:61887 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/alsa-2026:61887</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834)
  * kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)
  * kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454)
  * kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450)
  * kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)
  * kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() (CVE-2026-46120)
  * kernel: iommu/amd: Fix clone_alias() to use the original device&amp;#39;s devid (CVE-2026-53053)
  * kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026)
  * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)
  * kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196)
  * kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)
  * kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)
  * kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)
  * kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 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: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834)
  * kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)
  * kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454)
  * kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450)
  * kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)
  * kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() (CVE-2026-46120)
  * kernel: iommu/amd: Fix clone_alias() to use the original device&amp;#39;s devid (CVE-2026-53053)
  * kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026)
  * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)
  * kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196)
  * kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)
  * kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)
  * kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)
  * kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/alsa-2026:61887</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-72130</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-72130</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://vulnerability.circl.lu/vuln/bell-cve-2026-72130</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069</link>
      <description>certfr-2026-avi-1069</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72130</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-72130</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet-auth: reject short AUTH_RECEIVE buffers&lt;/p&gt;
&lt;p&gt;nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length
after checking only that it is nonzero and matches the transfer length.
In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF
initiator reach the fixed-size DH-HMAC-CHAP response builders with a
kmalloc() buffer shorter than the response, so nvmet_auth_success1() and
nvmet_auth_failure1() write past the allocation; both only WARN_ON the
short length and then format the message anyway.&lt;/p&gt;
&lt;p&gt;Impact: A remote NVMe-oF initiator with access to an auth-enabled target
can trigger a 16-byte heap out-of-bounds write via a one-byte
AUTH_RECEIVE allocation length.&lt;/p&gt;
&lt;p&gt;Compute the minimum response length for the current DH-HMAC-CHAP step in
nvmet_auth_receive_data_len() and report a zero data length when the
host-supplied allocation length is shorter, so the existing zero-length
check in nvmet_execute_auth_receive() rejects the command before any
builder runs. The SUCCESS1 minimum is sizeof(struct
nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the
response hash is written into the rval[] flexible-array tail, so the
minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its
existing variable-length guard in nvmet_auth_challenge().&lt;/p&gt;
&lt;p&gt;This is reachable only when in-band DH-HMAC-CHAP authentication is
configured on the target.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet-auth: reject short AUTH_RECEIVE buffers&lt;/p&gt;
&lt;p&gt;nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length
after checking only that it is nonzero and matches the transfer length.
In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF
initiator reach the fixed-size DH-HMAC-CHAP response builders with a
kmalloc() buffer shorter than the response, so nvmet_auth_success1() and
nvmet_auth_failure1() write past the allocation; both only WARN_ON the
short length and then format the message anyway.&lt;/p&gt;
&lt;p&gt;Impact: A remote NVMe-oF initiator with access to an auth-enabled target
can trigger a 16-byte heap out-of-bounds write via a one-byte
AUTH_RECEIVE allocation length.&lt;/p&gt;
&lt;p&gt;Compute the minimum response length for the current DH-HMAC-CHAP step in
nvmet_auth_receive_data_len() and report a zero data length when the
host-supplied allocation length is shorter, so the existing zero-length
check in nvmet_execute_auth_receive() rejects the command before any
builder runs. The SUCCESS1 minimum is sizeof(struct
nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the
response hash is written into the rval[] flexible-array tail, so the
minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its
existing variable-length guard in nvmet_auth_challenge().&lt;/p&gt;
&lt;p&gt;This is reachable only when in-band DH-HMAC-CHAP authentication is
configured on the target.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-72130</guid>
    </item>
    <item>
      <title>GHSA-m9xx-q2g4-96mr</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-m9xx-q2g4-96mr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet-auth: reject short AUTH_RECEIVE buffers&lt;/p&gt;
&lt;p&gt;nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length
after checking only that it is nonzero and matches the transfer length.
In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF
initiator reach the fixed-size DH-HMAC-CHAP response builders with a
kmalloc() buffer shorter than the response, so nvmet_auth_success1() and
nvmet_auth_failure1() write past the allocation; both only WARN_ON the
short length and then format the message anyway.&lt;/p&gt;
&lt;p&gt;Impact: A remote NVMe-oF initiator with access to an auth-enabled target
can trigger a 16-byte heap out-of-bounds write via a one-byte
AUTH_RECEIVE allocation length.&lt;/p&gt;
&lt;p&gt;Compute the minimum response length for the current DH-HMAC-CHAP step in
nvmet_auth_receive_data_len() and report a zero data length when the
host-supplied allocation length is shorter, so the existing zero-length
check in nvmet_execute_auth_receive() rejects the command before any
builder runs. The SUCCESS1 minimum is sizeof(struct
nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the
response hash is written into the rval[] flexible-array tail, so the
minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its
existing variable-length guard in nvmet_auth_challenge().&lt;/p&gt;
&lt;p&gt;This is reachable only when in-band DH-HMAC-CHAP authentication is
configured on the target.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet-auth: reject short AUTH_RECEIVE buffers&lt;/p&gt;
&lt;p&gt;nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length
after checking only that it is nonzero and matches the transfer length.
In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF
initiator reach the fixed-size DH-HMAC-CHAP response builders with a
kmalloc() buffer shorter than the response, so nvmet_auth_success1() and
nvmet_auth_failure1() write past the allocation; both only WARN_ON the
short length and then format the message anyway.&lt;/p&gt;
&lt;p&gt;Impact: A remote NVMe-oF initiator with access to an auth-enabled target
can trigger a 16-byte heap out-of-bounds write via a one-byte
AUTH_RECEIVE allocation length.&lt;/p&gt;
&lt;p&gt;Compute the minimum response length for the current DH-HMAC-CHAP step in
nvmet_auth_receive_data_len() and report a zero data length when the
host-supplied allocation length is shorter, so the existing zero-length
check in nvmet_execute_auth_receive() rejects the command before any
builder runs. The SUCCESS1 minimum is sizeof(struct
nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the
response hash is written into the rval[] flexible-array tail, so the
minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its
existing variable-length guard in nvmet_auth_challenge().&lt;/p&gt;
&lt;p&gt;This is reachable only when in-band DH-HMAC-CHAP authentication is
configured on the target.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-m9xx-q2g4-96mr</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-72130 — nvmet-auth: reject short AUTH_RECEIVE buffers</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-72130</link>
      <description>msrc_CVE-2026-72130</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-72130</guid>
    </item>
    <item>
      <title>RHSA-2026:61887 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2026:61887</link>
      <description>&lt;p&gt;kernel: seccomp: passthrough uretprobe systemcall without filtering kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg kernel: iommu/amd: Fix clone_alias() to use the original device&amp;#39;s devid kernel: mm/list_lru: drain before clearing xarray entry on reparent kernel: zram: fix use-after-free in zram_bvec_write_partial() kernel: mm/huge_memory: update file PMD counter before folio_put() kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr kernel: NFSv4/flexfiles: reject zero filehandle version count kernel: nfsd: fix posix_acl leak on SETACL decode failure kernel: nfsd: release layout stid on setlease failure kernel: pNFS: Fix use-after-free in pnfs_update_layout() kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access kernel: smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() kernel: netfilter: ipset: fix race between dump and ip_set_list resize kernel: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count kernel: Input: synaptics-rmi4 - bound the F3A keymap to t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: seccomp: passthrough uretprobe systemcall without filtering kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg kernel: iommu/amd: Fix clone_alias() to use the original device&amp;#39;s devid kernel: mm/list_lru: drain before clearing xarray entry on reparent kernel: zram: fix use-after-free in zram_bvec_write_partial() kernel: mm/huge_memory: update file PMD counter before folio_put() kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr kernel: NFSv4/flexfiles: reject zero filehandle version count kernel: nfsd: fix posix_acl leak on SETACL decode failure kernel: nfsd: release layout stid on setlease failure kernel: pNFS: Fix use-after-free in pnfs_update_layout() kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access kernel: smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() kernel: netfilter: ipset: fix race between dump and ip_set_list resize kernel: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count kernel: Input: synaptics-rmi4 - bound the F3A keymap to t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2026:61887</guid>
    </item>
    <item>
      <title>RLSA-2026:61887 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rlsa-2026:61887</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&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: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834)&lt;/p&gt;
&lt;p&gt;* kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450)&lt;/p&gt;
&lt;p&gt;* kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)&lt;/p&gt;
&lt;p&gt;* kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() (CVE-2026-46120)&lt;/p&gt;
&lt;p&gt;* kernel: iommu/amd: Fix clone_alias() to use the original device&amp;#39;s devid (CVE-2026-53053)&lt;/p&gt;
&lt;p&gt;* kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026)&lt;/p&gt;
&lt;p&gt;* kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)&lt;/p&gt;
&lt;p&gt;* kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196)&lt;/p&gt;
&lt;p&gt;* kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)&lt;/p&gt;
&lt;p&gt;* kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153)&lt;/p&gt;
&lt;p&gt;* kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)&lt;/p&gt;
&lt;p&gt;* kernel: NF…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&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: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834)&lt;/p&gt;
&lt;p&gt;* kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450)&lt;/p&gt;
&lt;p&gt;* kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)&lt;/p&gt;
&lt;p&gt;* kernel: ip6_gre: Use cached t-&amp;gt;net in ip6erspan_changelink() (CVE-2026-46120)&lt;/p&gt;
&lt;p&gt;* kernel: iommu/amd: Fix clone_alias() to use the original device&amp;#39;s devid (CVE-2026-53053)&lt;/p&gt;
&lt;p&gt;* kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026)&lt;/p&gt;
&lt;p&gt;* kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)&lt;/p&gt;
&lt;p&gt;* kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196)&lt;/p&gt;
&lt;p&gt;* kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)&lt;/p&gt;
&lt;p&gt;* kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153)&lt;/p&gt;
&lt;p&gt;* kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)&lt;/p&gt;
&lt;p&gt;* kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)&lt;/p&gt;
&lt;p&gt;* kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)&lt;/p&gt;
&lt;p&gt;* kernel: NF…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rlsa-2026:61887</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72130</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72130</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: reject short AUTH_RECEIVE buffers nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length after checking only that it is nonzero and matches the transfer length. In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF initiator reach the fixed-size DH-HMAC-CHAP response builders with a kmalloc() buffer shorter than the response, so nvmet_auth_success1() and nvmet_auth_failure1() write past the allocation; both only WARN_ON the short length and then format the message anyway. Impact: A remote NVMe-oF initiator with access to an auth-enabled target can trigger a 16-byte heap out-of-bounds write via a one-byte AUTH_RECEIVE allocation length. Compute the minimum response length for the current DH-HMAC-CHAP step in nvmet_auth_receive_data_len() and report a zero data length when the host-supplied allocation length is shorter, so the existing zero-length check in nvmet_execute_auth_receive() rejects the command before any builder runs. The SUCCESS1 minimum is sizeof(struct nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the response hash is written into the rval[] flexible-array tail, so the minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its existing variable-length guard in nvmet_auth_challenge(). This is reachable only when in-band DH-HMAC-CHAP authentication is configured on the target.&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: reject short AUTH_RECEIVE buffers nvmet_execute_auth_receive() trusts the AUTH_RECEIVE allocation length after checking only that it is nonzero and matches the transfer length. In the SUCCESS1 and FAILURE1/default states, that lets a remote NVMe-oF initiator reach the fixed-size DH-HMAC-CHAP response builders with a kmalloc() buffer shorter than the response, so nvmet_auth_success1() and nvmet_auth_failure1() write past the allocation; both only WARN_ON the short length and then format the message anyway. Impact: A remote NVMe-oF initiator with access to an auth-enabled target can trigger a 16-byte heap out-of-bounds write via a one-byte AUTH_RECEIVE allocation length. Compute the minimum response length for the current DH-HMAC-CHAP step in nvmet_auth_receive_data_len() and report a zero data length when the host-supplied allocation length is shorter, so the existing zero-length check in nvmet_execute_auth_receive() rejects the command before any builder runs. The SUCCESS1 minimum is sizeof(struct nvmf_auth_dhchap_success1_data) plus the HMAC hash length, because the response hash is written into the rval[] flexible-array tail, so the minimum is state dependent rather than a flat sizeof. CHALLENGE keeps its existing variable-length guard in nvmet_auth_challenge(). This is reachable only when in-band DH-HMAC-CHAP authentication is configured on the target.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72130</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
