<?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 06:47:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58099 — vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-58099</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2024-58099</guid>
    </item>
  </channel>
</rss>
