Full vulnerability report · 2026

CVE-2026-43147High confidence

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV"

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:Low, lowered one band.downgradedsince 23 May 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.10% for the current model date.

Compensating controls

Validate the affected product branch and deploy the verified fixed release.
Restrict local access and enforce least privilege on affected hosts.
Monitor vendor guidance and exploitation sources for a material change.

Verification

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Canonical Ubuntu Security: 19 affected package states with no published fix

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

23 package states

Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 19 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.85-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.170-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.6-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.6-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

CVE-2026-43147 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-43147

75 known affected

The vendor explicitly identifies these products as affected by this CVE.

cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise Live Patching 12 SP5

Summary: 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 > /sys/bus/pci/devices/ /sriov_numvfs $ echo 1 > /sys/bus/pci/devices/ /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: [ ] dump_stack_lvl+0xc0/0x110 [ ] print_deadlock_bug+0x31e/0x330 [ ] __lock_acquire+0x16c8/0x32f0 [ ] lock_acquire+0x14c/0x350 [ ] __mutex_lock_common+0xe6/0x1520 [ ] mutex_lock_nested+0x3c/0x50 [ ] sriov_disable+0x34/0x140 [ ] mlx5_sriov_disable+0x50/0x80 [mlx5_core] [ ] remove_one+0x5e/0xf0 [mlx5_core] [ ] pci_device_remove+0x3c/0xa0 [ ] device_release_driver_internal+0x18e/0x280 [ ] pci_stop_bus_device+0x82/0xa0 [ ] pci_stop_and_remove_bus_device_locked+0x5e/0x80 [ ] remove_store+0x72/0x90 [ ] kernfs_fop_write_iter+0x15a/0x200 [ ] vfs_write+0x24c/0x300 [ ] ksys_write+0x86/0x110 [ ] __do_syscall+0x14c/0x400 [ ] 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.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

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 <NUM> > /sys/bus/pci/devices/<pf>/sriov_numvfs $ echo 1 > /sys/bus/pci/devices/<pf>/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: [<00000259778c4f90>] dump_stack_lvl+0xc0/0x110 [<00000259779c844e>] print_deadlock_bug+0x31e/0x330 [<00000259779c1908>] __lock_acquire+0x16c8/0x32f0 [<00000259779bffac>] lock_acquire+0x14c/0x350 [<00000259789643a6>] __mutex_lock_common+0xe6/0x1520 [<000002597896413c>] mutex_lock_nested+0x3c/0x50 [<00000259784a07e4>] sriov_disable+0x34/0x140 [<00000258f7d6dd80>] mlx5_sriov_disable+0x50/0x80 [mlx5_core] [<00000258f7d5745e>] remove_one+0x5e/0xf0 [mlx5_core] [<00000259784857fc>] pci_device_remove+0x3c/0xa0 [<000002597851012e>] device_release_driver_internal+0x18e/0x280 [<000002597847ae22>] pci_stop_bus_device+0x82/0xa0 [<000002597847afce>] pci_stop_and_remove_bus_device_locked+0x5e/0x80 [<00000259784972c2>] remove_store+0x72/0x90 [<0000025977e6661a>] kernfs_fop_write_iter+0x15a/0x200 [<0000025977d7241c>] vfs_write+0x24c/0x300 [<0000025977d72696>] ksys_write+0x86/0x110 [<000002597895b61c>] __do_syscall+0x14c/0x400 [<000002597896e0ee>] 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.

What

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-667 ↗
CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-667

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-27707Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-1405Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43132 Référence CVE CVE-2026-43133 https://www.cve.org/CVERecord?id=CVE-2026-43133 Référence CVE CVE-2026-43134 https://www.cve.org/CVERecord?id=CVE-2026-43134 Référence CVE CVE-2026-43135 https://www.cve.org/CVERecord?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43133 Référence CVE CVE-2026-43134 https://www.cve.org/CVERecord?id=CVE-2026-43134 Référence CVE CVE-2026-43135 https://www.cve.org/CVERecord?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43137 https://www.cve.org/CVERecord?id=CVE-2026-43137 Référence CVE CVE-2026-43138 https://www.cve.org/CVERecord?id=CVE-2026-43138 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43143 https://www.cve.org/CVERecord?id=CVE-2026-43143 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43162 https://www.cve.org/CVERecord?id=CVE-2026-43162 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43169 https://www.cve.org/CVERecord?id=CVE-2026-43169 Référence CVE CVE-2026-43170 https://www.cve.org/CVERecord?id=CVE-2026-43170 Référence CVE CVE-2026-43172 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43134 Référence CVE CVE-2026-43135 https://www.cve.org/CVERecord?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43137 https://www.cve.org/CVERecord?id=CVE-2026-43137 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43143 https://www.cve.org/CVERecord?id=CVE-2026-43143 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43150 https://www.cve.org/CVERecord?id=CVE-2026-43150 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43153 https://www.cve.org/CVERecord?id=CVE-2026-43153 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43157 https://www.cve.org/CVERecord?id=CVE-2026-43157 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43134 Référence CVE CVE-2026-43135 https://www.cve.org/CVERecord?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43137 https://www.cve.org/CVERecord?id=CVE-2026-43137 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43143 https://www.cve.org/CVERecord?id=CVE-2026-43143 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43157 https://www.cve.org/CVERecord?id=CVE-2026-43157 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43161 https://www.cve.org/CVERecord?id=CVE-2026-43161 Référence CVE CVE-2026-43162 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43132 Référence CVE CVE-2026-43133 https://www.cve.org/CVERecord?id=CVE-2026-43133 Référence CVE CVE-2026-43134 https://www.cve.org/CVERecord?id=CVE-2026-43134 Référence CVE CVE-2026-43135 https://www.cve.org/CVERecord?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43162 https://www.cve.org/CVERecord?id=CVE-2026-43162 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0861Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0831Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0696Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-43124 Référence CVE CVE-2026-43130 https://www.cve.org/CVERecord?id=CVE-2026-43130 Référence CVE CVE-2026-43132 https://www.cve.org/CVERecord?id=CVE-2026-43132 Référence CVE CVE-2026-43134 https://www.cve.org/CVERecord?id=CVE-2026-43134 Référence CVE CVE-2026-43135 https://www.cve.org/CVERecord?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-015633LinuxのLinux Kernelにおけるリソースのロックに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が解決されました：PCI/IOVに関する問題です。SR-IOVの有効化および無効化時にPCIの再スキャン・削除ロックを追加するコミット（05703271c3cd）が取り消されました。この取り消しは、pci_stop_and_remove_bus_device()の一部としてsriov_del_vfs()が呼び出される際に、pci_rescan_remove_lockを再帰的に取得してデッドロックを引き起こす問題を修正します。例えば、以下のコマンドシーケンスで問題が発生します：$ echo NUM /sys/bus/pci/devices/pf/sriov_numvfs　$ echo 1 /sys/bus/pci/devices/pf/remove。mlx5デバイスでのデッドロックのトレース（一部抜粋）では、zsh/5715がsriov_disable関数内でpci_rescan_remove_lockの取得を試みている一方で、既にpci_stop_and_remove_bus_device_locked内で同じロックを保持している状態が示されています。この問題を解決するための新しい修正が今後提供される予定であり、今回の変更だけでは完全な解決策にはなりません。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix availability varies by product
Affected: cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise Live Patching 12 SP5
kernel-default-kgraft as component of SUSE Linux Enterprise Live Patching 12 SP5
kernel-default-kgraft-devel as component of SUSE Linux Enterprise Live Patching 12 SP5
kernel-source as component of SUSE Linux Enterprise Live Patching 12 SP5
cluster-md-kmp-default as component of SUSE Linux Enterprise Server 12 SP5-LTSS
dlm-kmp-default as component of SUSE Linux Enterprise Server 12 SP5-LTSS
gfs2-kmp-default as component of SUSE Linux Enterprise Server 12 SP5-LTSS
kernel-default as component of SUSE Linux Enterprise Server 12 SP5-LTSS
kernel-default-base as component of SUSE Linux Enterprise Server 12 SP5-LTSS
kernel-default-devel as component of SUSE Linux Enterprise Server 12 SP5-LTSS
kernel-default-man as component of SUSE Linux Enterprise Server 12 SP5-LTSS
kernel-devel as component of SUSE Linux Enterprise Server 12 SP5-LTSS
kernel-macros as component of SUSE Linux Enterprise Server 12 SP5-LTSS
kernel-source as component of SUSE Linux Enterprise Server 12 SP5-LTSS
ocfs2-kmp-default as component of SUSE Linux Enterprise Server 12 SP5-LTSS
cluster-md-kmp-default as component of SUSE Linux Enterprise Server 12 SP5
dlm-kmp-default as component of SUSE Linux Enterprise Server 12 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise Server 12 SP5
kernel-default as component of SUSE Linux Enterprise Server 12 SP5
and 45 more
Fixed: Linux: < 6.18, 5.10.252 ≤ 5.10.*, 5.15.202 ≤ 5.15.*, 6.1.165 ≤ 6.1.*, 6.6.128 ≤ 6.6.*, 6.12.75 ≤ 6.12.*, 6.18.16 ≤ 6.18.*, 6.19.6 ≤ 6.19.*, 7.0 ≤ *
Action: Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 6 May 2026 · Last source change 23 May 2026, 16:06 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2026-27707

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceNIST NVD

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2026-05-06CVE published

2026-05-23Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-27707↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV"

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2026-27707

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication