<?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>Tue, 29 Sep 2026 21:09:51 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:64770 — Important: kernel-rt security update</title>
      <link>https://vulnerability.circl.lu/vuln/alsa-2026:64770</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)
  * kernel: netfilter: conntrack: remove sprintf usage (CVE-2026-53002)
  * kernel: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (CVE-2026-64007)
  * kernel: rhashtable: clear stale iter-&amp;gt;p on table restart (CVE-2026-64563)
  * kernel: smb: client: validate DFS referral PathConsumed (CVE-2026-68343)
  * kernel: nvmet-rdma: handle inline data with a nonzero offset (CVE-2026-72129)
  * kernel: net: bridge: stop fast-leave after deleting a port group (CVE-2026-74480)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)
  * kernel: netfilter: conntrack: remove sprintf usage (CVE-2026-53002)
  * kernel: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (CVE-2026-64007)
  * kernel: rhashtable: clear stale iter-&amp;gt;p on table restart (CVE-2026-64563)
  * kernel: smb: client: validate DFS referral PathConsumed (CVE-2026-68343)
  * kernel: nvmet-rdma: handle inline data with a nonzero offset (CVE-2026-72129)
  * kernel: net: bridge: stop fast-leave after deleting a port group (CVE-2026-74480)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/alsa-2026:64770</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-72129</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-72129</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-72129</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1161 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1161</link>
      <description>certfr-2026-avi-1161</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1161</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72129</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-72129</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet-rdma: handle inline data with a nonzero offset&lt;/p&gt;
&lt;p&gt;nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset
into the per-command inline scatterlist.  The bounds check admits any
offset with off + len &amp;lt;= inline_data_size, but the mapping still assumes
the data begins in the first inline page:&lt;/p&gt;
&lt;p&gt;sg-&amp;gt;offset = off;
	sg-&amp;gt;length = min_t(int, len, PAGE_SIZE - off);&lt;/p&gt;
&lt;p&gt;When a port is configured with inline_data_size &amp;gt; PAGE_SIZE (settable up
to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size]
makes &amp;#34;PAGE_SIZE - off&amp;#34; underflow, so sg-&amp;gt;length is set to ~4 GiB and
the block backend reads far past the first inline page.  num_pages(len)
also ignores the offset, so an in-bounds offset whose [off, off+len)
span crosses a page boundary under-counts the scatterlist.&lt;/p&gt;
&lt;p&gt;Map the offset properly: split it into a page index and an in-page
offset, start the scatterlist at that page, and size the page count from
page_off + len.  Because the request scatterlist may now start at
inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL
identity test in nvmet_rdma_release_rsp() to a range test; otherwise the
persistent inline scatterlist is mistaken for an allocated one and
nvmet_req_free_sgls() frees an inline page (and warns in
free_large_kmalloc()).&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-rdma: handle inline data with a nonzero offset&lt;/p&gt;
&lt;p&gt;nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset
into the per-command inline scatterlist.  The bounds check admits any
offset with off + len &amp;lt;= inline_data_size, but the mapping still assumes
the data begins in the first inline page:&lt;/p&gt;
&lt;p&gt;sg-&amp;gt;offset = off;
	sg-&amp;gt;length = min_t(int, len, PAGE_SIZE - off);&lt;/p&gt;
&lt;p&gt;When a port is configured with inline_data_size &amp;gt; PAGE_SIZE (settable up
to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size]
makes &amp;#34;PAGE_SIZE - off&amp;#34; underflow, so sg-&amp;gt;length is set to ~4 GiB and
the block backend reads far past the first inline page.  num_pages(len)
also ignores the offset, so an in-bounds offset whose [off, off+len)
span crosses a page boundary under-counts the scatterlist.&lt;/p&gt;
&lt;p&gt;Map the offset properly: split it into a page index and an in-page
offset, start the scatterlist at that page, and size the page count from
page_off + len.  Because the request scatterlist may now start at
inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL
identity test in nvmet_rdma_release_rsp() to a range test; otherwise the
persistent inline scatterlist is mistaken for an allocated one and
nvmet_req_free_sgls() frees an inline page (and warns in
free_large_kmalloc()).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-72129</guid>
    </item>
    <item>
      <title>GHSA-xp9m-f2x6-j3rp</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-xp9m-f2x6-j3rp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet-rdma: handle inline data with a nonzero offset&lt;/p&gt;
&lt;p&gt;nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset
into the per-command inline scatterlist.  The bounds check admits any
offset with off + len &amp;lt;= inline_data_size, but the mapping still assumes
the data begins in the first inline page:&lt;/p&gt;
&lt;p&gt;sg-&amp;gt;offset = off;
	sg-&amp;gt;length = min_t(int, len, PAGE_SIZE - off);&lt;/p&gt;
&lt;p&gt;When a port is configured with inline_data_size &amp;gt; PAGE_SIZE (settable up
to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size]
makes &amp;#34;PAGE_SIZE - off&amp;#34; underflow, so sg-&amp;gt;length is set to ~4 GiB and
the block backend reads far past the first inline page.  num_pages(len)
also ignores the offset, so an in-bounds offset whose [off, off+len)
span crosses a page boundary under-counts the scatterlist.&lt;/p&gt;
&lt;p&gt;Map the offset properly: split it into a page index and an in-page
offset, start the scatterlist at that page, and size the page count from
page_off + len.  Because the request scatterlist may now start at
inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL
identity test in nvmet_rdma_release_rsp() to a range test; otherwise the
persistent inline scatterlist is mistaken for an allocated one and
nvmet_req_free_sgls() frees an inline page (and warns in
free_large_kmalloc()).&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-rdma: handle inline data with a nonzero offset&lt;/p&gt;
&lt;p&gt;nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset
into the per-command inline scatterlist.  The bounds check admits any
offset with off + len &amp;lt;= inline_data_size, but the mapping still assumes
the data begins in the first inline page:&lt;/p&gt;
&lt;p&gt;sg-&amp;gt;offset = off;
	sg-&amp;gt;length = min_t(int, len, PAGE_SIZE - off);&lt;/p&gt;
&lt;p&gt;When a port is configured with inline_data_size &amp;gt; PAGE_SIZE (settable up
to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size]
makes &amp;#34;PAGE_SIZE - off&amp;#34; underflow, so sg-&amp;gt;length is set to ~4 GiB and
the block backend reads far past the first inline page.  num_pages(len)
also ignores the offset, so an in-bounds offset whose [off, off+len)
span crosses a page boundary under-counts the scatterlist.&lt;/p&gt;
&lt;p&gt;Map the offset properly: split it into a page index and an in-page
offset, start the scatterlist at that page, and size the page count from
page_off + len.  Because the request scatterlist may now start at
inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL
identity test in nvmet_rdma_release_rsp() to a range test; otherwise the
persistent inline scatterlist is mistaken for an allocated one and
nvmet_req_free_sgls() frees an inline page (and warns in
free_large_kmalloc()).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-xp9m-f2x6-j3rp</guid>
    </item>
    <item>
      <title>OESA-2026-3703 — kernel security update</title>
      <link>https://vulnerability.circl.lu/vuln/oesa-2026-3703</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;ASoC: qcom: Fix sc7280 lpass potential buffer overflow&lt;/p&gt;
&lt;p&gt;Case values introduced in commit
5f78e1fb7a3e (&amp;amp;quot;ASoC: qcom: Add driver support for audioreach solution&amp;amp;quot;)
cause out of bounds access in arrays of sc7280 driver data (e.g. in case
of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).&lt;/p&gt;
&lt;p&gt;Redefine LPASS_MAX_PORTS to consider the maximum possible port id for
q6dsp as sc7280 driver utilizes some of those values.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37979)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization&lt;/p&gt;
&lt;p&gt;Syzbot reported shift-out-of-bounds exception on MDIO bus initialization.&lt;/p&gt;
&lt;p&gt;The PHY address should be masked to 5 bits (0-31). Without this
mask, invalid PHY addresses could be used, potentially causing issues
with MDIO bus operations.&lt;/p&gt;
&lt;p&gt;Fix this by masking the PHY address with 0x1f (31 decimal) to ensure
it stays within the valid range.(CVE-2025-38736)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl&lt;/p&gt;
&lt;p&gt;When page reassignment was added to af_alg_pull_tsgl the original
loop wasn&amp;amp;apos;t updated so it may try to reassign one more page than
necessary.&lt;/p&gt;
&lt;p&gt;Add the check to the reassignment so that this does not happen.&lt;/p&gt;
&lt;p&gt;Also u…&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;ASoC: qcom: Fix sc7280 lpass potential buffer overflow&lt;/p&gt;
&lt;p&gt;Case values introduced in commit
5f78e1fb7a3e (&amp;amp;quot;ASoC: qcom: Add driver support for audioreach solution&amp;amp;quot;)
cause out of bounds access in arrays of sc7280 driver data (e.g. in case
of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).&lt;/p&gt;
&lt;p&gt;Redefine LPASS_MAX_PORTS to consider the maximum possible port id for
q6dsp as sc7280 driver utilizes some of those values.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37979)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization&lt;/p&gt;
&lt;p&gt;Syzbot reported shift-out-of-bounds exception on MDIO bus initialization.&lt;/p&gt;
&lt;p&gt;The PHY address should be masked to 5 bits (0-31). Without this
mask, invalid PHY addresses could be used, potentially causing issues
with MDIO bus operations.&lt;/p&gt;
&lt;p&gt;Fix this by masking the PHY address with 0x1f (31 decimal) to ensure
it stays within the valid range.(CVE-2025-38736)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl&lt;/p&gt;
&lt;p&gt;When page reassignment was added to af_alg_pull_tsgl the original
loop wasn&amp;amp;apos;t updated so it may try to reassign one more page than
necessary.&lt;/p&gt;
&lt;p&gt;Add the check to the reassignment so that this does not happen.&lt;/p&gt;
&lt;p&gt;Also u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/oesa-2026-3703</guid>
    </item>
    <item>
      <title>RHSA-2026:64770 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2026:64770</link>
      <description>&lt;p&gt;kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests kernel: netfilter: conntrack: remove sprintf usage kernel: netfilter: synproxy: refresh tcphdr after skb_ensure_writable kernel: rhashtable: clear stale iter-&amp;gt;p on table restart kernel: smb: client: validate DFS referral PathConsumed kernel: nvmet-rdma: handle inline data with a nonzero offset kernel: net: bridge: stop fast-leave after deleting a port group&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests kernel: netfilter: conntrack: remove sprintf usage kernel: netfilter: synproxy: refresh tcphdr after skb_ensure_writable kernel: rhashtable: clear stale iter-&amp;gt;p on table restart kernel: smb: client: validate DFS referral PathConsumed kernel: nvmet-rdma: handle inline data with a nonzero offset kernel: net: bridge: stop fast-leave after deleting a port group&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2026:64770</guid>
    </item>
    <item>
      <title>RHSA-2026:65334 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2026:65334</link>
      <description>&lt;p&gt;kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation kernel: Bluetooth: SMP: force responder MITM requirements before building the pairing response kernel: Bluetooth: virtio_bt: clamp rx length before skb_put kernel: Bluetooth: serialize accept_q access kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove kernel: Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER kernel: net: pull headers in qdisc_pkt_len_segs_init() kernel: wifi: nl80211: reject oversized EMA RNR lists kernel: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers kernel: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() kernel: vfio/pci: Clean up DMABUFs before disabling function kernel: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync kernel: Bluetooth: ISO: fix UAF in iso_recv_frame kernel: Bluetooth: HIDP: fix missing length checks in hidp_input_report() kernel: Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp kernel: security/keys: fix missed RCU read section on lookup kernel: wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled kernel: vfio/pci: Check BAR resources before exporting a DMABUF kernel: accel/qaic: Add overflow check to remap_pfn_range during mmap kernel: ixgbevf: fix use-after-free in VEPA multicast source pruning kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb kernel: wifi: iwlwi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation kernel: Bluetooth: SMP: force responder MITM requirements before building the pairing response kernel: Bluetooth: virtio_bt: clamp rx length before skb_put kernel: Bluetooth: serialize accept_q access kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove kernel: Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER kernel: net: pull headers in qdisc_pkt_len_segs_init() kernel: wifi: nl80211: reject oversized EMA RNR lists kernel: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend kernel: Bluetooth: RFCOMM: validate skb length in MCC handlers kernel: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() kernel: vfio/pci: Clean up DMABUFs before disabling function kernel: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync kernel: Bluetooth: ISO: fix UAF in iso_recv_frame kernel: Bluetooth: HIDP: fix missing length checks in hidp_input_report() kernel: Bluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp kernel: security/keys: fix missed RCU read section on lookup kernel: wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled kernel: vfio/pci: Check BAR resources before exporting a DMABUF kernel: accel/qaic: Add overflow check to remap_pfn_range during mmap kernel: ixgbevf: fix use-after-free in VEPA multicast source pruning kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb kernel: wifi: iwlwi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2026:65334</guid>
    </item>
    <item>
      <title>RLSA-2026:64770 — Important: kernel-rt security update</title>
      <link>https://vulnerability.circl.lu/vuln/rlsa-2026:64770</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: conntrack: remove sprintf usage (CVE-2026-53002)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (CVE-2026-64007)&lt;/p&gt;
&lt;p&gt;* kernel: rhashtable: clear stale iter-&amp;gt;p on table restart (CVE-2026-64563)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: validate DFS referral PathConsumed (CVE-2026-68343)&lt;/p&gt;
&lt;p&gt;* kernel: nvmet-rdma: handle inline data with a nonzero offset (CVE-2026-72129)&lt;/p&gt;
&lt;p&gt;* kernel: net: bridge: stop fast-leave after deleting a port group (CVE-2026-74480)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel-rt&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: crypto: pcrypt - Fix handling of MAY_BACKLOG requests (CVE-2026-43493)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: conntrack: remove sprintf usage (CVE-2026-53002)&lt;/p&gt;
&lt;p&gt;* kernel: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (CVE-2026-64007)&lt;/p&gt;
&lt;p&gt;* kernel: rhashtable: clear stale iter-&amp;gt;p on table restart (CVE-2026-64563)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: validate DFS referral PathConsumed (CVE-2026-68343)&lt;/p&gt;
&lt;p&gt;* kernel: nvmet-rdma: handle inline data with a nonzero offset (CVE-2026-72129)&lt;/p&gt;
&lt;p&gt;* kernel: net: bridge: stop fast-leave after deleting a port group (CVE-2026-74480)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rlsa-2026:64770</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72129</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72129</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmet-rdma: handle inline data with a nonzero offset nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset into the per-command inline scatterlist.  The bounds check admits any offset with off + len &amp;lt;= inline_data_size, but the mapping still assumes the data begins in the first inline page: 	sg-&amp;gt;offset = off; 	sg-&amp;gt;length = min_t(int, len, PAGE_SIZE - off); When a port is configured with inline_data_size &amp;gt; PAGE_SIZE (settable up to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size] makes &amp;#34;PAGE_SIZE - off&amp;#34; underflow, so sg-&amp;gt;length is set to ~4 GiB and the block backend reads far past the first inline page.  num_pages(len) also ignores the offset, so an in-bounds offset whose [off, off+len) span crosses a page boundary under-counts the scatterlist. Map the offset properly: split it into a page index and an in-page offset, start the scatterlist at that page, and size the page count from page_off + len.  Because the request scatterlist may now start at inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL identity test in nvmet_rdma_release_rsp() to a range test; otherwise the persistent inline scatterlist is mistaken for an allocated one and nvmet_req_free_sgls() frees an inline page (and warns in free_large_kmalloc()).&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmet-rdma: handle inline data with a nonzero offset nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset into the per-command inline scatterlist.  The bounds check admits any offset with off + len &amp;lt;= inline_data_size, but the mapping still assumes the data begins in the first inline page: 	sg-&amp;gt;offset = off; 	sg-&amp;gt;length = min_t(int, len, PAGE_SIZE - off); When a port is configured with inline_data_size &amp;gt; PAGE_SIZE (settable up to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size] makes &amp;#34;PAGE_SIZE - off&amp;#34; underflow, so sg-&amp;gt;length is set to ~4 GiB and the block backend reads far past the first inline page.  num_pages(len) also ignores the offset, so an in-bounds offset whose [off, off+len) span crosses a page boundary under-counts the scatterlist. Map the offset properly: split it into a page index and an in-page offset, start the scatterlist at that page, and size the page count from page_off + len.  Because the request scatterlist may now start at inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL identity test in nvmet_rdma_release_rsp() to a range test; otherwise the persistent inline scatterlist is mistaken for an allocated one and nvmet_req_free_sgls() frees an inline page (and warns in free_large_kmalloc()).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72129</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>
