{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43147 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-43147 is a medium-severity vulnerability in Linux kernel, published on 6 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-43147 and fix it if it is affected.\n\nWhat it is: CVE-2026-43147 is a medium-severity vulnerability in Linux kernel, published on 6 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-43147 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-43147/ (Markdown: https://insights.sbomify.com/CVE-2026-43147/index.md)","id":"CVE-2026-43147","markdown":"https://insights.sbomify.com/CVE-2026-43147/index.md","name":"CVE-2026-43147","record":{"aliases":["BELL-CVE-2026-43147","DEBIAN-CVE-2026-43147","GHSA-5c36-jx4m-m84f","ROOT-OS-DEBIAN-11-CVE-2026-43147","ROOT-OS-UBUNTU-2204-CVE-2026-43147","ROOT-OS-UBUNTU-2404-CVE-2026-43147","UBUNTU-CVE-2026-43147"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A deadlock in the Linux kernel PCI subsystem allows local attackers to cause a denial of service by triggering recursive locking during SR-IOV device removal.","user_interaction":"not_required","vuln_class":"race_condition"},"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":[{"id":"CWE-667","name":"Improper Locking"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\"\n\nThis reverts commit 05703271c3cd (\"PCI/IOV: Add PCI rescan-remove locking\nwhen enabling/disabling SR-IOV\"), which causes a deadlock by recursively\ntaking pci_rescan_remove_lock when sriov_del_vfs() is called as part of\npci_stop_and_remove_bus_device(). For example with the following sequence\nof commands:\n\n  $ echo \u003cNUM\u003e \u003e /sys/bus/pci/devices/\u003cpf\u003e/sriov_numvfs\n  $ echo 1 \u003e /sys/bus/pci/devices/\u003cpf\u003e/remove\n\nA trimmed trace of the deadlock on a mlx5 device is as below:\n\n  zsh/5715 is trying to acquire lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140\n\n  but task is already holding lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_stop_and_remove_bus_device_locked+0x24/0x80\n  ...\n  Call Trace:\n   [\u003c00000259778c4f90\u003e] dump_stack_lvl+0xc0/0x110\n   [\u003c00000259779c844e\u003e] print_deadlock_bug+0x31e/0x330\n   [\u003c00000259779c1908\u003e] __lock_acquire+0x16c8/0x32f0\n   [\u003c00000259779bffac\u003e] lock_acquire+0x14c/0x350\n   [\u003c00000259789643a6\u003e] __mutex_lock_common+0xe6/0x1520\n   [\u003c000002597896413c\u003e] mutex_lock_nested+0x3c/0x50\n   [\u003c00000259784a07e4\u003e] sriov_disable+0x34/0x140\n   [\u003c00000258f7d6dd80\u003e] mlx5_sriov_disable+0x50/0x80 [mlx5_core]\n   [\u003c00000258f7d5745e\u003e] remove_one+0x5e/0xf0 [mlx5_core]\n   [\u003c00000259784857fc\u003e] pci_device_remove+0x3c/0xa0\n   [\u003c000002597851012e\u003e] device_release_driver_internal+0x18e/0x280\n   [\u003c000002597847ae22\u003e] pci_stop_bus_device+0x82/0xa0\n   [\u003c000002597847afce\u003e] pci_stop_and_remove_bus_device_locked+0x5e/0x80\n   [\u003c00000259784972c2\u003e] remove_store+0x72/0x90\n   [\u003c0000025977e6661a\u003e] kernfs_fop_write_iter+0x15a/0x200\n   [\u003c0000025977d7241c\u003e] vfs_write+0x24c/0x300\n   [\u003c0000025977d72696\u003e] ksys_write+0x86/0x110\n   [\u003c000002597895b61c\u003e] __do_syscall+0x14c/0x400\n   [\u003c000002597896e0ee\u003e] system_call+0x6e/0x90\n\nThis alone is not a complete fix as it restores the issue the cited commit\ntried to solve. A new fix will be provided as a follow on.","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":"Revert \"PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\"","id":"CVE-2026-43147","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"powerpc/smp: Add check for kcalloc() failure in parse_thread_groups()","id":"CVE-2026-43148"},"packages":[],"prev":{"headline":"media: iris: Add buffer to list only after successful allocation","id":"CVE-2026-43146"},"products":["Linux"],"published":"2026-05-06","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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 deadlock in the Linux kernel PCI subsystem allows local attackers to cause a denial of service by triggering recursive locking during SR-IOV device removal.","url":"https://insights.sbomify.com/CVE-2026-43147/"}