{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.170-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.6-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  Revert \"PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\"  This reverts commit 05703271c3cd (\"PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\"), which causes a deadlock by recursively taking pci_rescan_remove_lock when sriov_del_vfs() is called as part of pci_stop_and_remove_bus_device(). For example with the following sequence of commands:    $ echo \u003cNUM\u003e \u003e /sys/bus/pci/devices/\u003cpf\u003e/sriov_numvfs   $ echo 1 \u003e /sys/bus/pci/devices/\u003cpf\u003e/remove  A trimmed trace of the deadlock on a mlx5 device is as below:    zsh/5715 is trying to acquire lock:   000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140    but task is already holding lock:   000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_stop_and_remove_bus_device_locked+0x24/0x80   ...   Call Trace:    [\u003c00000259778c4f90\u003e] dump_stack_lvl+0xc0/0x110    [\u003c00000259779c844e\u003e] print_deadlock_bug+0x31e/0x330    [\u003c00000259779c1908\u003e] __lock_acquire+0x16c8/0x32f0    [\u003c00000259779bffac\u003e] lock_acquire+0x14c/0x350    [\u003c00000259789643a6\u003e] __mutex_lock_common+0xe6/0x1520    [\u003c000002597896413c\u003e] mutex_lock_nested+0x3c/0x50    [\u003c00000259784a07e4\u003e] sriov_disable+0x34/0x140    [\u003c00000258f7d6dd80\u003e] mlx5_sriov_disable+0x50/0x80 [mlx5_core]    [\u003c00000258f7d5745e\u003e] remove_one+0x5e/0xf0 [mlx5_core]    [\u003c00000259784857fc\u003e] pci_device_remove+0x3c/0xa0    [\u003c000002597851012e\u003e] device_release_driver_internal+0x18e/0x280    [\u003c000002597847ae22\u003e] pci_stop_bus_device+0x82/0xa0    [\u003c000002597847afce\u003e] pci_stop_and_remove_bus_device_locked+0x5e/0x80    [\u003c00000259784972c2\u003e] remove_store+0x72/0x90    [\u003c0000025977e6661a\u003e] kernfs_fop_write_iter+0x15a/0x200    [\u003c0000025977d7241c\u003e] vfs_write+0x24c/0x300    [\u003c0000025977d72696\u003e] ksys_write+0x86/0x110    [\u003c000002597895b61c\u003e] __do_syscall+0x14c/0x400    [\u003c000002597896e0ee\u003e] system_call+0x6e/0x90  This alone is not a complete fix as it restores the issue the cited commit tried to solve. A new fix will be provided as a follow on.",
  "id": "DEBIAN-CVE-2026-43147",
  "modified": "2026-09-14T16:47:34.461743954Z",
  "published": "2026-05-06T12:16:32.240Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-43147"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-43147"
  ]
}