<?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://cve.radiocsirt.org</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, 03 Oct 2026 15:08:01 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-06041</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-06041</link>
      <description>bdu:2026-06041</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-06041</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-58099</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-58099</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-58099</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0529 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</link>
      <description>certfr-2025-avi-0529</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</guid>
    </item>
    <item>
      <title>EUVD-2026-346604</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346604</link>
      <description>EUVD-2026-346604</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346604</guid>
    </item>
    <item>
      <title>fkie_cve-2024-58099</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-58099</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame&lt;/p&gt;
&lt;p&gt;Andrew and Nikolay reported connectivity issues with Cilium&amp;#39;s service
load-balancing in case of vmxnet3.&lt;/p&gt;
&lt;p&gt;If a BPF program for native XDP adds an encapsulation header such as
IPIP and transmits the packet out the same interface, then in case
of vmxnet3 a corrupted packet is being sent and subsequently dropped
on the path.&lt;/p&gt;
&lt;p&gt;vmxnet3_xdp_xmit_frame() which is called e.g. via vmxnet3_run_xdp()
through vmxnet3_xdp_xmit_back() calculates an incorrect DMA address:&lt;/p&gt;
&lt;p&gt;page = virt_to_page(xdpf-&amp;gt;data);
  tbi-&amp;gt;dma_addr = page_pool_get_dma_addr(page) +
                  VMXNET3_XDP_HEADROOM;
  dma_sync_single_for_device(&amp;amp;adapter-&amp;gt;pdev-&amp;gt;dev,
                             tbi-&amp;gt;dma_addr, buf_size,
                             DMA_TO_DEVICE);&lt;/p&gt;
&lt;p&gt;The above assumes a fixed offset (VMXNET3_XDP_HEADROOM), but the XDP
BPF program could have moved xdp-&amp;gt;data. While the passed buf_size is
correct (xdpf-&amp;gt;len), the dma_addr needs to have a dynamic offset which
can be calculated as xdpf-&amp;gt;data - (void *)xdpf, that is, xdp-&amp;gt;data -
xdp-&amp;gt;data_hard_start.&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;vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame&lt;/p&gt;
&lt;p&gt;Andrew and Nikolay reported connectivity issues with Cilium&amp;#39;s service
load-balancing in case of vmxnet3.&lt;/p&gt;
&lt;p&gt;If a BPF program for native XDP adds an encapsulation header such as
IPIP and transmits the packet out the same interface, then in case
of vmxnet3 a corrupted packet is being sent and subsequently dropped
on the path.&lt;/p&gt;
&lt;p&gt;vmxnet3_xdp_xmit_frame() which is called e.g. via vmxnet3_run_xdp()
through vmxnet3_xdp_xmit_back() calculates an incorrect DMA address:&lt;/p&gt;
&lt;p&gt;page = virt_to_page(xdpf-&amp;gt;data);
  tbi-&amp;gt;dma_addr = page_pool_get_dma_addr(page) +
                  VMXNET3_XDP_HEADROOM;
  dma_sync_single_for_device(&amp;amp;adapter-&amp;gt;pdev-&amp;gt;dev,
                             tbi-&amp;gt;dma_addr, buf_size,
                             DMA_TO_DEVICE);&lt;/p&gt;
&lt;p&gt;The above assumes a fixed offset (VMXNET3_XDP_HEADROOM), but the XDP
BPF program could have moved xdp-&amp;gt;data. While the passed buf_size is
correct (xdpf-&amp;gt;len), the dma_addr needs to have a dynamic offset which
can be calculated as xdpf-&amp;gt;data - (void *)xdpf, that is, xdp-&amp;gt;data -
xdp-&amp;gt;data_hard_start.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-58099</guid>
    </item>
    <item>
      <title>GHSA-274g-94c9-xmph</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-274g-94c9-xmph</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame&lt;/p&gt;
&lt;p&gt;Andrew and Nikolay reported connectivity issues with Cilium&amp;#39;s service
load-balancing in case of vmxnet3.&lt;/p&gt;
&lt;p&gt;If a BPF program for native XDP adds an encapsulation header such as
IPIP and transmits the packet out the same interface, then in case
of vmxnet3 a corrupted packet is being sent and subsequently dropped
on the path.&lt;/p&gt;
&lt;p&gt;vmxnet3_xdp_xmit_frame() which is called e.g. via vmxnet3_run_xdp()
through vmxnet3_xdp_xmit_back() calculates an incorrect DMA address:&lt;/p&gt;
&lt;p&gt;page = virt_to_page(xdpf-&amp;gt;data);
  tbi-&amp;gt;dma_addr = page_pool_get_dma_addr(page) +
                  VMXNET3_XDP_HEADROOM;
  dma_sync_single_for_device(&amp;amp;adapter-&amp;gt;pdev-&amp;gt;dev,
                             tbi-&amp;gt;dma_addr, buf_size,
                             DMA_TO_DEVICE);&lt;/p&gt;
&lt;p&gt;The above assumes a fixed offset (VMXNET3_XDP_HEADROOM), but the XDP
BPF program could have moved xdp-&amp;gt;data. While the passed buf_size is
correct (xdpf-&amp;gt;len), the dma_addr needs to have a dynamic offset which
can be calculated as xdpf-&amp;gt;data - (void *)xdpf, that is, xdp-&amp;gt;data -
xdp-&amp;gt;data_hard_start.&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;vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame&lt;/p&gt;
&lt;p&gt;Andrew and Nikolay reported connectivity issues with Cilium&amp;#39;s service
load-balancing in case of vmxnet3.&lt;/p&gt;
&lt;p&gt;If a BPF program for native XDP adds an encapsulation header such as
IPIP and transmits the packet out the same interface, then in case
of vmxnet3 a corrupted packet is being sent and subsequently dropped
on the path.&lt;/p&gt;
&lt;p&gt;vmxnet3_xdp_xmit_frame() which is called e.g. via vmxnet3_run_xdp()
through vmxnet3_xdp_xmit_back() calculates an incorrect DMA address:&lt;/p&gt;
&lt;p&gt;page = virt_to_page(xdpf-&amp;gt;data);
  tbi-&amp;gt;dma_addr = page_pool_get_dma_addr(page) +
                  VMXNET3_XDP_HEADROOM;
  dma_sync_single_for_device(&amp;amp;adapter-&amp;gt;pdev-&amp;gt;dev,
                             tbi-&amp;gt;dma_addr, buf_size,
                             DMA_TO_DEVICE);&lt;/p&gt;
&lt;p&gt;The above assumes a fixed offset (VMXNET3_XDP_HEADROOM), but the XDP
BPF program could have moved xdp-&amp;gt;data. While the passed buf_size is
correct (xdpf-&amp;gt;len), the dma_addr needs to have a dynamic offset which
can be calculated as xdpf-&amp;gt;data - (void *)xdpf, that is, xdp-&amp;gt;data -
xdp-&amp;gt;data_hard_start.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-274g-94c9-xmph</guid>
    </item>
    <item>
      <title>OESA-2025-1463 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1463</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;PCI/ASPM: Fix link state exit during switch upstream function removal&lt;/p&gt;
&lt;p&gt;Before 456d8aa37d0f (&amp;amp;quot;PCI/ASPM: Disable ASPM on MFD function removal to
avoid use-after-free&amp;amp;quot;), we would free the ASPM link only after the last
function on the bus pertaining to the given link was removed.&lt;/p&gt;
&lt;p&gt;That was too late. If function 0 is removed before sibling function,
link-&amp;amp;gt;downstream would point to free&amp;amp;apos;d memory after.&lt;/p&gt;
&lt;p&gt;After above change, we freed the ASPM parent link state upon any function
removal on the bus pertaining to a given link.&lt;/p&gt;
&lt;p&gt;That is too early. If the link is to a PCIe switch with MFD on the upstream
port, then removing functions other than 0 first would free a link which
still remains parent_link to the remaining downstream ports.&lt;/p&gt;
&lt;p&gt;The resulting GPFs are especially frequent during hot-unplug, because
pciehp removes devices on the link bus in reverse order.&lt;/p&gt;
&lt;p&gt;On that switch, function 0 is the virtual P2P bridge to the internal bus.
Free exactly when function 0 is removed -- before the parent link is
obsolete, but after all subordinate links are gone.&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2024-58093)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jfs: add check read-only before truncation in jfs_truncate_nolock()&lt;/p&gt;
&lt;p&gt;Added a check for &amp;amp;quot;read-only&amp;amp;quot; mode in the `jfs_truncate_nolock`
function to avoid errors…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;PCI/ASPM: Fix link state exit during switch upstream function removal&lt;/p&gt;
&lt;p&gt;Before 456d8aa37d0f (&amp;amp;quot;PCI/ASPM: Disable ASPM on MFD function removal to
avoid use-after-free&amp;amp;quot;), we would free the ASPM link only after the last
function on the bus pertaining to the given link was removed.&lt;/p&gt;
&lt;p&gt;That was too late. If function 0 is removed before sibling function,
link-&amp;amp;gt;downstream would point to free&amp;amp;apos;d memory after.&lt;/p&gt;
&lt;p&gt;After above change, we freed the ASPM parent link state upon any function
removal on the bus pertaining to a given link.&lt;/p&gt;
&lt;p&gt;That is too early. If the link is to a PCIe switch with MFD on the upstream
port, then removing functions other than 0 first would free a link which
still remains parent_link to the remaining downstream ports.&lt;/p&gt;
&lt;p&gt;The resulting GPFs are especially frequent during hot-unplug, because
pciehp removes devices on the link bus in reverse order.&lt;/p&gt;
&lt;p&gt;On that switch, function 0 is the virtual P2P bridge to the internal bus.
Free exactly when function 0 is removed -- before the parent link is
obsolete, but after all subordinate links are gone.&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2024-58093)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jfs: add check read-only before truncation in jfs_truncate_nolock()&lt;/p&gt;
&lt;p&gt;Added a check for &amp;amp;quot;read-only&amp;amp;quot; mode in the `jfs_truncate_nolock`
function to avoid errors…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1463</guid>
    </item>
    <item>
      <title>RHSA-2025:6966 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:6966</link>
      <description>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:6966</guid>
    </item>
    <item>
      <title>RHSA-2025:9584 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:9584</link>
      <description>&lt;p&gt;kernel: SUNRPC: Fix a suspicious RCU usage warning kernel: drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node kernel: nbd: always initialize struct msghdr completely kernel: net/sched: flower: Fix chain template offload kernel: drm/i915/vma: Fix UAF on destroy against retire race kernel: wifi: mac80211: fix potential sta-link leak kernel: irqchip/gic-v3-its: Prevent double free on error kernel: block: fix overflow in blk_ioctl_discard() kernel: netfilter: nf_tables: prefer nft_chain_validate kernel: bpf: fix OOB devmap writes when deleting elements kernel: vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame kernel: ndisc: use RCU protection in ndisc_alloc_skb() kernel: sched/rt: Fix race in push_rt_task&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: SUNRPC: Fix a suspicious RCU usage warning kernel: drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node kernel: nbd: always initialize struct msghdr completely kernel: net/sched: flower: Fix chain template offload kernel: drm/i915/vma: Fix UAF on destroy against retire race kernel: wifi: mac80211: fix potential sta-link leak kernel: irqchip/gic-v3-its: Prevent double free on error kernel: block: fix overflow in blk_ioctl_discard() kernel: netfilter: nf_tables: prefer nft_chain_validate kernel: bpf: fix OOB devmap writes when deleting elements kernel: vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame kernel: ndisc: use RCU protection in ndisc_alloc_skb() kernel: sched/rt: Fix race in push_rt_task&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:9584</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01964-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01964-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:01964-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-58099</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58099</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame Andrew and Nikolay reported connectivity issues with Cilium&amp;#39;s service load-balancing in case of vmxnet3. If a BPF program for native XDP adds an encapsulation header such as IPIP and transmits the packet out the same interface, then in case of vmxnet3 a corrupted packet is being sent and subsequently dropped on the path. vmxnet3_xdp_xmit_frame() which is called e.g. via vmxnet3_run_xdp() through vmxnet3_xdp_xmit_back() calculates an incorrect DMA address:   page = virt_to_page(xdpf-&amp;gt;data);   tbi-&amp;gt;dma_addr = page_pool_get_dma_addr(page) +                   VMXNET3_XDP_HEADROOM;   dma_sync_single_for_device(&amp;amp;adapter-&amp;gt;pdev-&amp;gt;dev,                              tbi-&amp;gt;dma_addr, buf_size,                              DMA_TO_DEVICE); The above assumes a fixed offset (VMXNET3_XDP_HEADROOM), but the XDP BPF program could have moved xdp-&amp;gt;data. While the passed buf_size is correct (xdpf-&amp;gt;len), the dma_addr needs to have a dynamic offset which can be calculated as xdpf-&amp;gt;data - (void *)xdpf, that is, xdp-&amp;gt;data - xdp-&amp;gt;data_hard_start.&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame Andrew and Nikolay reported connectivity issues with Cilium&amp;#39;s service load-balancing in case of vmxnet3. If a BPF program for native XDP adds an encapsulation header such as IPIP and transmits the packet out the same interface, then in case of vmxnet3 a corrupted packet is being sent and subsequently dropped on the path. vmxnet3_xdp_xmit_frame() which is called e.g. via vmxnet3_run_xdp() through vmxnet3_xdp_xmit_back() calculates an incorrect DMA address:   page = virt_to_page(xdpf-&amp;gt;data);   tbi-&amp;gt;dma_addr = page_pool_get_dma_addr(page) +                   VMXNET3_XDP_HEADROOM;   dma_sync_single_for_device(&amp;amp;adapter-&amp;gt;pdev-&amp;gt;dev,                              tbi-&amp;gt;dma_addr, buf_size,                              DMA_TO_DEVICE); The above assumes a fixed offset (VMXNET3_XDP_HEADROOM), but the XDP BPF program could have moved xdp-&amp;gt;data. While the passed buf_size is correct (xdpf-&amp;gt;len), the dma_addr needs to have a dynamic offset which can be calculated as xdpf-&amp;gt;data - (void *)xdpf, that is, xdp-&amp;gt;data - xdp-&amp;gt;data_hard_start.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58099</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0904 — Linux Kernel: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0904</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0904</guid>
    </item>
  </channel>
</rss>
