{"api_version":"1","generated_at":"2026-05-11T11:03:43+00:00","cve":"CVE-2026-43464","urls":{"html":"https://cve.report/CVE-2026-43464","api":"https://cve.report/api/cve/CVE-2026-43464.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-43464","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-43464"},"summary":{"title":"net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ\n\nXDP multi-buf programs can modify the layout of the XDP buffer when the\nprogram calls bpf_xdp_pull_data() or bpf_xdp_adjust_tail(). The\nreferenced commit in the fixes tag corrected the assumption in the mlx5\ndriver that the XDP buffer layout doesn't change during a program\nexecution. However, this fix introduced another issue: the dropped\nfragments still need to be counted on the driver side to avoid page\nfragment reference counting issues.\n\nSuch issue can be observed with the\ntest_xdp_native_adjst_tail_shrnk_data selftest when using a payload of\n3600 and shrinking by 256 bytes (an upcoming selftest patch): the last\nfragment gets released by the XDP code but doesn't get tracked by the\ndriver. This results in a negative pp_ref_count during page release and\nthe following splat:\n\n  WARNING: include/net/page_pool/helpers.h:297 at mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core], CPU#12: ip/3137\n  Modules linked in: [...]\n  CPU: 12 UID: 0 PID: 3137 Comm: ip Not tainted 6.19.0-rc3+ #12 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n  RIP: 0010:mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core]\n  [...]\n  Call Trace:\n   <TASK>\n   mlx5e_dealloc_rx_wqe+0xcb/0x1a0 [mlx5_core]\n   mlx5e_free_rx_descs+0x7f/0x110 [mlx5_core]\n   mlx5e_close_rq+0x50/0x60 [mlx5_core]\n   mlx5e_close_queues+0x36/0x2c0 [mlx5_core]\n   mlx5e_close_channel+0x1c/0x50 [mlx5_core]\n   mlx5e_close_channels+0x45/0x80 [mlx5_core]\n   mlx5e_safe_switch_params+0x1a5/0x230 [mlx5_core]\n   mlx5e_change_mtu+0xf3/0x2f0 [mlx5_core]\n   netif_set_mtu_ext+0xf1/0x230\n   do_setlink.isra.0+0x219/0x1180\n   rtnl_newlink+0x79f/0xb60\n   rtnetlink_rcv_msg+0x213/0x3a0\n   netlink_rcv_skb+0x48/0xf0\n   netlink_unicast+0x24a/0x350\n   netlink_sendmsg+0x1ee/0x410\n   __sock_sendmsg+0x38/0x60\n   ____sys_sendmsg+0x232/0x280\n   ___sys_sendmsg+0x78/0xb0\n   __sys_sendmsg+0x5f/0xb0\n   [...]\n   do_syscall_64+0x57/0xc50\n\nThis patch fixes the issue by doing page frag counting on all the\noriginal XDP buffer fragments for all relevant XDP actions (XDP_TX ,\nXDP_REDIRECT and XDP_PASS). This is basically reverting to the original\ncounting before the commit in the fixes tag.\n\nAs frag_page is still pointing to the original tail, the nr_frags\nparameter to xdp_update_skb_frags_info() needs to be calculated\nin a different way to reflect the new nr_frags.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-08 15:16:59","updated_at":"2026-05-11 08:16:15"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"baseScore":7.5,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/c74557495efb4bd0adefdfc8678ecdbc82a06da3","name":"https://git.kernel.org/stable/c/c74557495efb4bd0adefdfc8678ecdbc82a06da3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a6413e6f6c9d9bb9833324cb3753582f7bc0f2fa","name":"https://git.kernel.org/stable/c/a6413e6f6c9d9bb9833324cb3753582f7bc0f2fa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/03cb50e5b74fce8bf6d92b860371b66253cf0f8d","name":"https://git.kernel.org/stable/c/03cb50e5b74fce8bf6d92b860371b66253cf0f8d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-43464","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43464","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected afd5ba577c10639f62e8120df67dc70ea4b61176 c74557495efb4bd0adefdfc8678ecdbc82a06da3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected afd5ba577c10639f62e8120df67dc70ea4b61176 03cb50e5b74fce8bf6d92b860371b66253cf0f8d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected afd5ba577c10639f62e8120df67dc70ea4b61176 a6413e6f6c9d9bb9833324cb3753582f7bc0f2fa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 72328f25755ee966724f46e3a0e8e59bef2091ba git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0049fd63881505566824e88cfa624638f921c808 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d969645b9b7810289bf3c353ea06957373756b8e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.19 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.9 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"43464","cve":"CVE-2026-43464","epss":"0.000170000","percentile":"0.043040000","score_date":"2026-05-10","updated_at":"2026-05-11 00:14:41"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/net/ethernet/mellanox/mlx5/core/en_rx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"c74557495efb4bd0adefdfc8678ecdbc82a06da3","status":"affected","version":"afd5ba577c10639f62e8120df67dc70ea4b61176","versionType":"git"},{"lessThan":"03cb50e5b74fce8bf6d92b860371b66253cf0f8d","status":"affected","version":"afd5ba577c10639f62e8120df67dc70ea4b61176","versionType":"git"},{"lessThan":"a6413e6f6c9d9bb9833324cb3753582f7bc0f2fa","status":"affected","version":"afd5ba577c10639f62e8120df67dc70ea4b61176","versionType":"git"},{"status":"affected","version":"72328f25755ee966724f46e3a0e8e59bef2091ba","versionType":"git"},{"status":"affected","version":"0049fd63881505566824e88cfa624638f921c808","versionType":"git"},{"status":"affected","version":"d969645b9b7810289bf3c353ea06957373756b8e","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/net/ethernet/mellanox/mlx5/core/en_rx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.18"},{"lessThan":"6.18","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.19","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.9","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.19","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.9","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6.115","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.12.56","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.17.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ\n\nXDP multi-buf programs can modify the layout of the XDP buffer when the\nprogram calls bpf_xdp_pull_data() or bpf_xdp_adjust_tail(). The\nreferenced commit in the fixes tag corrected the assumption in the mlx5\ndriver that the XDP buffer layout doesn't change during a program\nexecution. However, this fix introduced another issue: the dropped\nfragments still need to be counted on the driver side to avoid page\nfragment reference counting issues.\n\nSuch issue can be observed with the\ntest_xdp_native_adjst_tail_shrnk_data selftest when using a payload of\n3600 and shrinking by 256 bytes (an upcoming selftest patch): the last\nfragment gets released by the XDP code but doesn't get tracked by the\ndriver. This results in a negative pp_ref_count during page release and\nthe following splat:\n\n  WARNING: include/net/page_pool/helpers.h:297 at mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core], CPU#12: ip/3137\n  Modules linked in: [...]\n  CPU: 12 UID: 0 PID: 3137 Comm: ip Not tainted 6.19.0-rc3+ #12 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n  RIP: 0010:mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core]\n  [...]\n  Call Trace:\n   <TASK>\n   mlx5e_dealloc_rx_wqe+0xcb/0x1a0 [mlx5_core]\n   mlx5e_free_rx_descs+0x7f/0x110 [mlx5_core]\n   mlx5e_close_rq+0x50/0x60 [mlx5_core]\n   mlx5e_close_queues+0x36/0x2c0 [mlx5_core]\n   mlx5e_close_channel+0x1c/0x50 [mlx5_core]\n   mlx5e_close_channels+0x45/0x80 [mlx5_core]\n   mlx5e_safe_switch_params+0x1a5/0x230 [mlx5_core]\n   mlx5e_change_mtu+0xf3/0x2f0 [mlx5_core]\n   netif_set_mtu_ext+0xf1/0x230\n   do_setlink.isra.0+0x219/0x1180\n   rtnl_newlink+0x79f/0xb60\n   rtnetlink_rcv_msg+0x213/0x3a0\n   netlink_rcv_skb+0x48/0xf0\n   netlink_unicast+0x24a/0x350\n   netlink_sendmsg+0x1ee/0x410\n   __sock_sendmsg+0x38/0x60\n   ____sys_sendmsg+0x232/0x280\n   ___sys_sendmsg+0x78/0xb0\n   __sys_sendmsg+0x5f/0xb0\n   [...]\n   do_syscall_64+0x57/0xc50\n\nThis patch fixes the issue by doing page frag counting on all the\noriginal XDP buffer fragments for all relevant XDP actions (XDP_TX ,\nXDP_REDIRECT and XDP_PASS). This is basically reverting to the original\ncounting before the commit in the fixes tag.\n\nAs frag_page is still pointing to the original tail, the nr_frags\nparameter to xdp_update_skb_frags_info() needs to be calculated\nin a different way to reflect the new nr_frags."}],"metrics":[{"cvssV3_1":{"baseScore":7.5,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"providerMetadata":{"dateUpdated":"2026-05-11T06:34:51.018Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/c74557495efb4bd0adefdfc8678ecdbc82a06da3"},{"url":"https://git.kernel.org/stable/c/03cb50e5b74fce8bf6d92b860371b66253cf0f8d"},{"url":"https://git.kernel.org/stable/c/a6413e6f6c9d9bb9833324cb3753582f7bc0f2fa"}],"title":"net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-43464","datePublished":"2026-05-08T14:22:26.039Z","dateReserved":"2026-05-01T14:12:56.011Z","dateUpdated":"2026-05-11T06:34:51.018Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-08 15:16:59","lastModifiedDate":"2026-05-11 08:16:15","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":3.6}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"43464","Ordinal":"1","Title":"net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ","CVE":"CVE-2026-43464","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"43464","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ\n\nXDP multi-buf programs can modify the layout of the XDP buffer when the\nprogram calls bpf_xdp_pull_data() or bpf_xdp_adjust_tail(). The\nreferenced commit in the fixes tag corrected the assumption in the mlx5\ndriver that the XDP buffer layout doesn't change during a program\nexecution. However, this fix introduced another issue: the dropped\nfragments still need to be counted on the driver side to avoid page\nfragment reference counting issues.\n\nSuch issue can be observed with the\ntest_xdp_native_adjst_tail_shrnk_data selftest when using a payload of\n3600 and shrinking by 256 bytes (an upcoming selftest patch): the last\nfragment gets released by the XDP code but doesn't get tracked by the\ndriver. This results in a negative pp_ref_count during page release and\nthe following splat:\n\n  WARNING: include/net/page_pool/helpers.h:297 at mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core], CPU#12: ip/3137\n  Modules linked in: [...]\n  CPU: 12 UID: 0 PID: 3137 Comm: ip Not tainted 6.19.0-rc3+ #12 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n  RIP: 0010:mlx5e_page_release_fragmented.isra.0+0x4a/0x50 [mlx5_core]\n  [...]\n  Call Trace:\n   <TASK>\n   mlx5e_dealloc_rx_wqe+0xcb/0x1a0 [mlx5_core]\n   mlx5e_free_rx_descs+0x7f/0x110 [mlx5_core]\n   mlx5e_close_rq+0x50/0x60 [mlx5_core]\n   mlx5e_close_queues+0x36/0x2c0 [mlx5_core]\n   mlx5e_close_channel+0x1c/0x50 [mlx5_core]\n   mlx5e_close_channels+0x45/0x80 [mlx5_core]\n   mlx5e_safe_switch_params+0x1a5/0x230 [mlx5_core]\n   mlx5e_change_mtu+0xf3/0x2f0 [mlx5_core]\n   netif_set_mtu_ext+0xf1/0x230\n   do_setlink.isra.0+0x219/0x1180\n   rtnl_newlink+0x79f/0xb60\n   rtnetlink_rcv_msg+0x213/0x3a0\n   netlink_rcv_skb+0x48/0xf0\n   netlink_unicast+0x24a/0x350\n   netlink_sendmsg+0x1ee/0x410\n   __sock_sendmsg+0x38/0x60\n   ____sys_sendmsg+0x232/0x280\n   ___sys_sendmsg+0x78/0xb0\n   __sys_sendmsg+0x5f/0xb0\n   [...]\n   do_syscall_64+0x57/0xc50\n\nThis patch fixes the issue by doing page frag counting on all the\noriginal XDP buffer fragments for all relevant XDP actions (XDP_TX ,\nXDP_REDIRECT and XDP_PASS). This is basically reverting to the original\ncounting before the commit in the fixes tag.\n\nAs frag_page is still pointing to the original tail, the nr_frags\nparameter to xdp_update_skb_frags_info() needs to be calculated\nin a different way to reflect the new nr_frags.","Type":"Description","Title":"net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ"}]}}}