CVE-2026-43464

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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: 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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
32.5%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 20, 2026

Advisory Details (3)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c74557495efb4bd0adefdfc8678ecdbc82a06da3
generic

net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6413e6f6c9d9bb9833324cb3753582f7bc0f2fa
generic

net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03cb50e5b74fce8bf6d92b860371b66253cf0f8d

Vendor Advisories for CVE-2026-43464(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 136 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:22 UTCEG score recompute
  20. 2026-06-28 04:22 UTCGHSA enrichment
  21. 2026-06-27 13:21 UTCEG score recompute
  22. 2026-06-27 13:21 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 21:20 UTCEG score recompute
  25. 2026-06-26 21:20 UTCGHSA enrichment
Show 75 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-24 14:05 UTCEPSS rescore
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-22 14:25 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-21 14:56 UTCEPSS rescore
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 01:59 UTCEPSS rescore
  10. 2026-06-19 19:25 UTCEPSS rescore
  11. 2026-06-18 17:52 UTCEPSS rescore
  12. 2026-06-18 17:52 UTCEPSS rescore
  13. 2026-06-17 17:53 UTCEPSS rescore
  14. 2026-06-17 01:28 UTCEG score recompute
  15. 2026-06-17 01:27 UTCGHSA enrichment
  16. 2026-06-16 17:52 UTCEPSS rescore
  17. 2026-06-16 08:07 UTCEG score recompute
  18. 2026-06-16 08:07 UTCGHSA enrichment
  19. 2026-06-15 17:49 UTCEPSS rescore
  20. 2026-06-15 02:23 UTCEG score recompute
  21. 2026-06-15 02:23 UTCGHSA enrichment
  22. 2026-06-14 14:50 UTCEG score recompute
  23. 2026-06-14 14:50 UTCGHSA enrichment
  24. 2026-06-14 02:33 UTCEG score recompute
  25. 2026-06-14 02:33 UTCGHSA enrichment
  26. 2026-06-13 23:00 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-12 20:37 UTCEG score recompute
  30. 2026-06-12 20:37 UTCGHSA enrichment
  31. 2026-06-12 09:05 UTCEG score recompute
  32. 2026-06-12 09:04 UTCGHSA enrichment
  33. 2026-06-11 21:26 UTCEG score recompute
  34. 2026-06-11 21:26 UTCGHSA enrichment
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-11 09:55 UTCEG score recompute
  37. 2026-06-11 09:55 UTCGHSA enrichment
  38. 2026-06-10 22:23 UTCEG score recompute
  39. 2026-06-10 22:23 UTCGHSA enrichment
  40. 2026-06-10 22:18 UTCEPSS rescore
  41. 2026-06-10 13:22 UTCEPSS rescore
  42. 2026-06-10 13:22 UTCEPSS rescore
  43. 2026-06-10 10:51 UTCEG score recompute
  44. 2026-06-10 10:51 UTCGHSA enrichment
  45. 2026-06-09 23:20 UTCEG score recompute
  46. 2026-06-09 23:20 UTCGHSA enrichment
  47. 2026-06-09 11:47 UTCEG score recompute
  48. 2026-06-09 11:47 UTCGHSA enrichment
  49. 2026-06-09 00:16 UTCEG score recompute
  50. 2026-06-09 00:16 UTCGHSA enrichment
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-08 14:17 UTCEPSS rescore
  53. 2026-06-08 12:44 UTCEG score recompute
  54. 2026-06-08 12:43 UTCGHSA enrichment
  55. 2026-06-08 01:11 UTCEG score recompute
  56. 2026-06-08 01:11 UTCGHSA enrichment
  57. 2026-06-07 15:25 UTCEPSS rescore
  58. 2026-06-07 15:25 UTCEPSS rescore
  59. 2026-06-07 13:40 UTCEG score recompute
  60. 2026-06-07 13:40 UTCGHSA enrichment
  61. 2026-06-07 02:08 UTCEG score recompute
  62. 2026-06-07 02:08 UTCGHSA enrichment
  63. 2026-06-06 14:36 UTCEG score recompute
  64. 2026-06-06 14:36 UTCGHSA enrichment
  65. 2026-06-06 13:47 UTCEPSS rescore
  66. 2026-06-06 13:47 UTCEPSS rescore
  67. 2026-06-06 03:04 UTCEG score recompute
  68. 2026-06-06 03:04 UTCGHSA enrichment
  69. 2026-06-05 22:47 UTCEPSS rescore
  70. 2026-06-05 15:32 UTCEG score recompute
  71. 2026-06-05 15:32 UTCGHSA enrichment
  72. 2026-06-05 06:10 UTCEPSS rescore
  73. 2026-06-05 06:10 UTCEPSS rescore
  74. 2026-06-05 04:00 UTCEG score recompute
  75. 2026-06-05 04:00 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-43464?
CVE-2026-43464 is a high vulnerability published on May 8, 2026. 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 bpfxdppulldata() or bpfxdpadjusttail(). The referenced commit in the fixes tag…
When was CVE-2026-43464 disclosed?
CVE-2026-43464 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43464 actively exploited?
CVE-2026-43464 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43464?
CVE-2026-43464 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-43464?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43464, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43464

Explore →

Is Your Infrastructure Affected by CVE-2026-43464?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs