{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43012 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-43012 is a medium-severity vulnerability in Linux kernel, published on 1 May 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-43012 and fix it if it is affected.\n\nWhat it is: CVE-2026-43012 is a medium-severity vulnerability in Linux kernel, published on 1 May 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-43012 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-43012/ (Markdown: https://insights.sbomify.com/CVE-2026-43012/index.md)","id":"CVE-2026-43012","markdown":"https://insights.sbomify.com/CVE-2026-43012/index.md","name":"CVE-2026-43012","record":{"aliases":["BELL-CVE-2026-43012","DEBIAN-CVE-2026-43012","GHSA-x4q9-gx2x-rgxq","ROOT-OS-UBUNTU-2404-CVE-2026-43012","UBUNTU-CVE-2026-43012"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A flaw in the mlx5 driver causes a kernel crash during switchdev mode rollback, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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/mlx5: Fix switchdev mode rollback in case of failure\n\nIf for some internal reason switchdev mode fails, we rollback to legacy\nmode, before this patch, rollback will unregister the uplink netdev and\nleave it unregistered causing the below kernel bug.\n\nTo fix this, we need to avoid netdev unregister by setting the proper\nrollback flag 'MLX5_PRIV_FLAGS_SWITCH_LEGACY' to indicate legacy mode.\n\ndevlink (431) used greatest stack depth: 11048 bytes left\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), \\\n\tnecvfs(0), active vports(0)\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nmlx5_core 0000:00:03.0: Loading uplink representor for vport 65535\nmlx5_core 0000:00:03.0: mlx5_cmd_out_err:816:(pid 456): \\\n\tQUERY_HCA_CAP(0x100) op_mod(0x0) failed, \\\n\tstatus bad parameter(0x3), syndrome (0x3a3846), err(-22)\nmlx5_core 0000:00:03.0 enp0s3np0 (unregistered): Unloading uplink \\\n\trepresentor for vport 65535\n ------------[ cut here ]------------\nkernel BUG at net/core/dev.c:12070!\nOops: invalid opcode: 0000 [#1] SMP NOPTI\nCPU: 2 UID: 0 PID: 456 Comm: devlink Not tainted 6.16.0-rc3+ \\\n\t#9 PREEMPT(voluntary)\nRIP: 0010:unregister_netdevice_many_notify+0x123/0xae0\n...\nCall Trace:\n[   90.923094]  unregister_netdevice_queue+0xad/0xf0\n[   90.923323]  unregister_netdev+0x1c/0x40\n[   90.923522]  mlx5e_vport_rep_unload+0x61/0xc6\n[   90.923736]  esw_offloads_enable+0x8e6/0x920\n[   90.923947]  mlx5_eswitch_enable_locked+0x349/0x430\n[   90.924182]  ? is_mp_supported+0x57/0xb0\n[   90.924376]  mlx5_devlink_eswitch_mode_set+0x167/0x350\n[   90.924628]  devlink_nl_eswitch_set_doit+0x6f/0xf0\n[   90.924862]  genl_family_rcv_msg_doit+0xe8/0x140\n[   90.925088]  genl_rcv_msg+0x18b/0x290\n[   90.925269]  ? __pfx_devlink_nl_pre_doit+0x10/0x10\n[   90.925506]  ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n[   90.925766]  ? __pfx_devlink_nl_post_doit+0x10/0x10\n[   90.926001]  ? __pfx_genl_rcv_msg+0x10/0x10\n[   90.926206]  netlink_rcv_skb+0x52/0x100\n[   90.926393]  genl_rcv+0x28/0x40\n[   90.926557]  netlink_unicast+0x27d/0x3d0\n[   90.926749]  netlink_sendmsg+0x1f7/0x430\n[   90.926942]  __sys_sendto+0x213/0x220\n[   90.927127]  ? __sys_recvmsg+0x6a/0xd0\n[   90.927312]  __x64_sys_sendto+0x24/0x30\n[   90.927504]  do_syscall_64+0x50/0x1c0\n[   90.927687]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   90.927929] RIP: 0033:0x7f7d0363e047","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: Fix switchdev mode rollback in case of failure","id":"CVE-2026-43012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"net/mlx5: lag: Check for LAG device before creating debugfs","id":"CVE-2026-43013"},"packages":[],"prev":{"headline":"net/x25: Fix potential double free of skb","id":"CVE-2026-43011"},"products":["Linux"],"published":"2026-05-01","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-05-23","vendors":["Linux"]},"summary":"A flaw in the mlx5 driver causes a kernel crash during switchdev mode rollback, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-43012/"}