Vulnerability · Published May 8, 2026 · Assigned by Linux

CVE-2026-43464net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ

High 7.5

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 46% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High
Exploit odds (30 days)0.5%top 54.0% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ XDP multi-buf programs can modify the layout of the XDP buffer when the program calls bpf_xdp_pull_data() or bpf_xdp_adjust_tail(). The referenced commit in the fixes tag corrected the assumption in the mlx5 driver that the XDP buffer layout doesn't change during a program execution. However, this fix introduced another issue: the dropped fragments still need to be counted on the driver side to avoid page fragment reference counting issues. Such issue can be observed with the test_xdp_native_adjst_tail_shrnk_data selftest when using a payload of 3600 and shrinking by 256 bytes (an upcoming selftest patch): the last fragment gets released by the XDP code but doesn't get tracked by the driver. This results in a negative pp_ref_count during page release and the following splat: WARNING: include/net/page_pool/helpers.h:297 at mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core], CPU#12: ip/3137 Modules linked in: [...] CPU: 12 UID: 0 PID: 3137 Comm: ip Not tainted 6.19.0-rc3+ #12 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core] [...] Call Trace: <TASK> mlx5e_dealloc_rx_wqe+0xcb/0x1a0 [mlx5_core] mlx5e_free_rx_descs+0x7f/0x110 [mlx5_core] mlx5e_close_rq+0x50/0x60 [mlx5_core] mlx5e_close_queues+0x36/0x2c0 [mlx5_core] mlx5e_close_channel+0x1c/0x50 [mlx5_core] mlx5e_close_channels+0x45/0x80 [mlx5_core] mlx5e_safe_switch_params+0x1a5/0x230 [mlx5_core] mlx5e_change_mtu+0xf3/0x2f0 [mlx5_core] netif_set_mtu_ext+0xf1/0x230 do_setlink.isra.0+0x219/0x1180 rtnl_newlink+0x79f/0xb60 rtnetlink_rcv_msg+0x213/0x3a0 netlink_rcv_skb+0x48/0xf0 netlink_unicast+0x24a/0x350 netlink_sendmsg+0x1ee/0x410 __sock_sendmsg+0x38/0x60 ____sys_sendmsg+0x232/0x280 ___sys_sendmsg+0x78/0xb0 __sys_sendmsg+0x5f/0xb0 [...] do_syscall_64+0x57/0xc50 This patch fixes the issue by doing page frag counting on all the original XDP buffer fragments for all relevant XDP actions (XDP_TX , XDP_REDIRECT and XDP_PASS). This is basically reverting to the original counting before the commit in the fixes tag. As frag_page is still pointing to the original tail, the nr_frags parameter to xdp_update_skb_frags_info() needs to be calculated in a different way to reflect the new nr_frags.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.115-2DEBIAN-CVE-2026-43464
Debian:14linux6.19.10-1DEBIAN-CVE-2026-43464
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1035.38UBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43464
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-43464
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-43464
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-43464

Affected products (as reported)

VendorProductVersions
Linux Linux 72328f25755ee966724f46e3a0e8e59bef2091ba – before 1106412414dc3ee62999115be10ca83199b021080049fd63881505566824e88cfa624638f921c808 – before 9488ee96b4f53d2aed474c744f0ed64f61d1dcc9afd5ba577c10639f62e8120df67dc70ea4b61176 – before c74557495efb4bd0adefdfc8678ecdbc82a06da3afd5ba577c10639f62e8120df67dc70ea4b61176 – before 03cb50e5b74fce8bf6d92b860371b66253cf0f8dafd5ba577c10639f62e8120df67dc70ea4b61176 – before a6413e6f6c9d9bb9833324cb3753582f7bc0f2fad969645b9b7810289bf3c353ea06957373756b8e6.6.115 – before 6.6.1606.12.56 – before 6.12.114
Linux Linux 6.18

References