net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Partial Red Hat: 2 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.
Summary
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Linux | Linux | 6.6.115 to before 6.6.160; 6.12.56 to before 6.12.114; 6.17.6 to before 6.18 | 6.6.160, 6.12.114, 6.18 | Patch available | CNA |
| Linux | Linux | 6.18 and later | 6.6.160, 6.12.114, 6.18.19, 6.19.9, 7.0 | Patch available | CNA |
- Linux VendorLinux Affected 6.6.115 to before 6.6.160; 6.12.56 to before 6.12.114; 6.17.6 to before 6.18 Fixed in 6.6.160, 6.12.114, 6.18 Patch available CNA
- Linux VendorLinux Affected 6.18 and later Fixed in 6.6.160, 6.12.114, 6.18.19, 6.19.9, 7.0 Patch available CNA
CPE configurations NVD · 10
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.6.115 to before 6.7; 6.12.56 to before 6.13; 6.17.6 to before 6.18; 6.18.1 to before 6.18.19; 6.19 to before 6.19.9 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:* | 6.18 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.18:rc3:*:*:*:*:*:* | 6.18 rc3 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:* | 6.18 rc4 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:* | 6.18 rc5 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:* | 6.18 rc6 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:6.18:rc7:*:*:*:*:*:* | 6.18 rc7 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* | 7.0 rc1 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* | 7.0 rc2 | Vulnerable | Linux |
| cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* | 7.0 rc3 | Vulnerable | Linux |
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions 6.6.115 to before 6.7; 6.12.56 to before 6.13; 6.17.6 to before 6.18; 6.18.1 to before 6.18.19; 6.19 to before 6.19.9 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:* Versions 6.18 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.18:rc3:*:*:*:*:*:* Versions 6.18 rc3 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:* Versions 6.18 rc4 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:* Versions 6.18 rc5 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:* Versions 6.18 rc6 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:6.18:rc7:*:*:*:*:*:* Versions 6.18 rc7 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* Versions 7.0 rc1 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* Versions 7.0 rc2 Vulnerable ·Linux
- cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* Versions 7.0 rc3 Vulnerable ·Linux
Remediation
- Fix · CNA Linux (Linux) Fixed in 6.6.160, 6.12.114, 6.18
- Fix · CNA Linux (Linux) Fixed in 6.6.160, 6.12.114, 6.18.19, 6.19.9, 7.0
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Enterprise Linux 10 | Affected | No fix yet: Fix deferred |
| Red Hat Enterprise Linux 6 | Affected | No fix planned: Out of support scope |
Not affected: 3 products
- Red Hat Enterprise Linux 7
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9
Timeline
- 2026-10-02 Threatist record created from CVE-2026-43464
- 2026-10-03 Alias added: GHSA-mf99-5486-2jh2
- 2026-10-21 Fix available: Linux/Linux@1106412414dc3ee62999115be10ca83199b02108, Linux/[email protected], Linux/[email protected] +1 · CNA
- 2026-10-21 2 new references · CNA
- 2026-10-25 EPSS moved to the below the 50th percentile
References
Patch 3
More Linux Kernel vulnerabilities
- TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
- TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
- TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
- TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
- TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
- TI-2021-05514 Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE KEVCVSS 3.1HIGH 8.3
Sources
- CVE-2026-43464 · CVE Program
- CVE-2026-43464 · NVD
- FIRST EPSS
- GHSA-mf99-5486-2jh2 · GitHub Advisory Database · CC BY 4.0
- CVE-2026-43464 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences