<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:38:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58099 — vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame</title>
      <link>https://db.gcve.eu/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://db.gcve.eu/vuln/cve-2024-58099</guid>
    </item>
    <item>
      <title>USN-7523-1 — linux-raspi-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7523-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:Realtime:24.04:LTS: linux-raspi-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - SuperH RISC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - RAM backed block device driver;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - TPM device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - ARM SCMI message protocol;
  - ARM SCPI message protocol;
  - EFI core;
  - iSCSI Boot Firmware Table Attributes driver;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Microchip PCI driver;
  - MMC subsystem;
  - MTD…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:Realtime:24.04:LTS: linux-raspi-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - SuperH RISC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - RAM backed block device driver;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - TPM device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - ARM SCMI message protocol;
  - ARM SCPI message protocol;
  - EFI core;
  - iSCSI Boot Firmware Table Attributes driver;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Microchip PCI driver;
  - MMC subsystem;
  - MTD…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7523-1</guid>
    </item>
  </channel>
</rss>
