{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43464 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-43464 is a high-severity use after free vulnerability in Linux kernel, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-43464 and fix it if it is affected.\n\nWhat it is: CVE-2026-43464 is a high-severity use after free vulnerability in Linux kernel, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-43464 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-43464/ (Markdown: https://insights.sbomify.com/CVE-2026-43464/index.md)","id":"CVE-2026-43464","markdown":"https://insights.sbomify.com/CVE-2026-43464/index.md","name":"CVE-2026-43464","record":{"aliases":["AZL-87057","BELL-CVE-2026-43464","DEBIAN-CVE-2026-43464","GHSA-mf99-5486-2jh2","ROOT-OS-DEBIAN-13-CVE-2026-43464","ROOT-OS-UBUNTU-2404-CVE-2026-43464","UBUNTU-CVE-2026-43464"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A reference counting error in the mlx5e driver can cause a use-after-free condition, leading to a kernel crash or denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"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   \u003cTASK\u003e\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"net/mlx5e: RX, Fix XDP multi-buf frag counting for legacy RQ","id":"CVE-2026-43464","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"net/mlx5e: RX, Fix XDP multi-buf frag counting for striding RQ","id":"CVE-2026-43465"},"packages":[],"prev":{"headline":"rxrpc, afs: Fix missing error pointer check after rxrpc_kernel_lookup_peer()","id":"CVE-2026-43463"},"products":["Linux"],"published":"2026-05-08","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A reference counting error in the mlx5e driver can cause a use-after-free condition, leading to a kernel crash or denial of service.","url":"https://insights.sbomify.com/CVE-2026-43464/"}