{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98014 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98014 is an use after free vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98014 and fix it if it is affected.\n\nWhat it is: CVE-2026-98014 is an use after free vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98014 in the wild and no public exploit code.\n\nAffected product: Linux. 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-98014/ (Markdown: https://insights.sbomify.com/CVE-2026-98014/index.md)","id":"CVE-2026-98014","markdown":"https://insights.sbomify.com/CVE-2026-98014/index.md","name":"CVE-2026-98014","record":{"aliases":["AZL-104759","BELL-CVE-2026-98014","DEBIAN-CVE-2026-98014","GHSA-hjxx-jpr5-hfgw","UBUNTU-CVE-2026-98014"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A use-after-free vulnerability in the Linux kernel mlx5 driver allows local attackers to cause a system crash or potentially execute code during vport disable operations.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: E-Switch, prevent mc_list repopulation during vport disable\n\nIn mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead\nof esw_vport_change_handle_locked() so vport-\u003eallmulti_rule is\nNULL before the change handler observes it.\n\nDuring FW-fatal recovery the disable runs while dev-\u003estate ==\nINTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode()\nfails and returns early, leaving vport-\u003eallmulti_rule intact, so\nesw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries\nto vport-\u003emc_list whose flow rules are then installed in the FDB\nby esw_add_mc_addr(). esw_destroy_legacy_table() tears down the\nFDB with those refs still held, corrupting the sub-tree and\nleaving dangling flow_rule pointers in vport-\u003emc_list.\n\nTwo-stage failure on `echo 1 \u003e /sys/bus/pci/devices/\u003cbdf\u003e/reset`:\n\n  refcount_t: underflow; use-after-free.\n   tree_put_node+0xef/0x110 [mlx5_core]\n   clean_tree+0x44/0xd0 [mlx5_core] (x5)\n   mlx5_fs_core_cleanup+0x57/0x1c0 [mlx5_core]\n   mlx5_unload+0x65/0xd0 [mlx5_core]\n   ... mlx5_health_try_recover\n\n  BUG: unable to handle page fault for address: 0000000003000055\n   down_write+0x1c/0x60\n   mlx5_del_flow_rules+0x33/0x1f0 [mlx5_core]\n   esw_del_mc_addr+0x7b/0x170 [mlx5_core]\n   esw_apply_vport_addr_list+0x56/0xf0 [mlx5_core]\n   esw_vport_change_handle_locked+0x28b/0x310 [mlx5_core]\n   mlx5_esw_vport_enable+0x270/0x4a0 [mlx5_core]\n   ... mlx5_load ... mlx5_health_try_recover\n\nesw_apply_vport_rx_mode(false, false) clears vport-\u003eallmulti_rule\nvia its local state machine even when the FW del fails. With the\nrule NULL the !IS_ERR_OR_NULL(allmulti_rule) gate in the change\nhandler closes, no rules are installed during disable, and the\nreload starts with a clean mc_list.","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/mlx5: E-Switch, prevent mc_list repopulation during vport disable","id":"CVE-2026-98014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put","id":"CVE-2026-98015"},"packages":[],"prev":{"headline":"net/sched: fq_pie: clamp quantum in change path","id":"CVE-2026-98013"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel mlx5 driver allows local attackers to cause a system crash or potentially execute code during vport disable operations.","url":"https://insights.sbomify.com/CVE-2026-98014/"}