Full vulnerability report · 2026

CVE-2026-45904High confidence

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling

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 20 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 27 May 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.16% 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Canonical Ubuntu Security: 20 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.

24 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 20 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 6 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 6 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.18.14-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.18.14-1`	Debian Security Tracker ↗Source updated 6 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-azure-nvidia-6.14`	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-45904 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-45904

17 known affected

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

SUSE Linux Micro Extras 6.2:kernel-obs-build
SUSE Linux Micro Extras 6.2:kernel-syms
SLES 15 SP1 CHOST Images for Amazon EC2
SLES 15 SP2 CHOST Images for Amazon EC2
SLES 15 SP3 CHOST Images for Amazon EC2
SLES 15 SP4 CHOST Images for Amazon EC2
SLES 15 SP5 CHOST Images for Amazon EC2
SLES 15 SP1 CHOST Images for Google
SLES 15 SP2 CHOST Images for Google
SLES 15 SP3 CHOST Images for Google
SLES 15 SP4 CHOST Images for Google
SLES 15 SP5 CHOST Images for Google

Summary: In the Linux kernel, the following vulnerability has been resolved: powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling The recent commit 1010b4c012b0 ("powerpc/eeh: Make EEH driver device hotplug safe") restructured the EEH driver to improve synchronization with the PCI hotplug layer. However, it inadvertently moved pci_lock_rescan_remove() outside its intended scope in eeh_handle_normal_event(), leading to broken PCI error reporting and improper EEH event triggering. Specifically, eeh_handle_normal_event() acquired pci_lock_rescan_remove() before calling eeh_pe_bus_get(), but eeh_pe_bus_get() itself attempts to acquire the same lock internally, causing nested locking and disrupting normal EEH event handling paths. This patch adds a boolean parameter do_lock to _eeh_pe_bus_get(), with two public wrappers: eeh_pe_bus_get() with locking enabled. eeh_pe_bus_get_nolock() that skips locking. Callers that already hold pci_lock_rescan_remove() now use eeh_pe_bus_get_nolock() to avoid recursive lock acquisition. Additionally, pci_lock_rescan_remove() calls are restored to the correct position-after eeh_pe_bus_get() and immediately before iterating affected PEs and devices. This ensures EEH-triggered PCI removes occur under proper bus rescan locking without recursive lock contention. The eeh_pe_loc_get() function has been split into two functions: eeh_pe_loc_get(struct eeh_pe *pe) which retrieves the loc for given PE. eeh_pe_loc_get_bus(struct pci_bus *bus) which retrieves the location code for given bus. This resolves lockdep warnings such as: [ 84.964298] [ T928] ============================================ [ 84.964304] [ T928] WARNING: possible recursive locking detected [ 84.964311] [ T928] 6.18.0-rc3 #51 Not tainted [ 84.964315] [ T928] -------------------------------------------- [ 84.964320] [ T928] eehd/928 is trying to acquire lock: [ 84.964324] [ T928] c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964342] [ T928] but task is already holding lock: [ 84.964347] [ T928] c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964357] [ T928] other info that might help us debug this: [ 84.964363] [ T928] Possible unsafe locking scenario: [ 84.964367] [ T928] CPU0 [ 84.964370] [ T928] ---- [ 84.964373] [ T928] lock(pci_rescan_remove_lock); [ 84.964378] [ T928] lock(pci_rescan_remove_lock); [ 84.964383] [ T928] *** DEADLOCK *** [ 84.964388] [ T928] May be due to missing lock nesting notation [ 84.964393] [ T928] 1 lock held by eehd/928: [ 84.964397] [ T928] #0: c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964408] [ T928] stack backtrace: [ 84.964414] [ T928] CPU: 2 UID: 0 PID: 928 Comm: eehd Not tainted 6.18.0-rc3 #51 VOLUNTARY [ 84.964417] [ T928] Hardware name: IBM,9080-HEX POWER10 (architected) 0x800200 0xf000006 of:IBM,FW1060.00 (NH1060_022) hv:phyp pSeries [ 84.964419] [ T928] Call Trace: [ 84.964420] [ T928] [c0000011a7157990] [c000000001705de4] dump_stack_lvl+0xc8/0x130 (unreliable) [ 84.964424] [ T928] [c0000011a71579d0] [c0000000002f66e0] print_deadlock_bug+0x430/0x440 [ 84.964428] [ T928] [c0000011a7157a70] [c0000000002fd0c0] __lock_acquire+0x1530/0x2d80 [ 84.964431] [ T928] [c0000011a7157ba0] [c0000000002fea54] lock_acquire+0x144/0x410 [ 84.964433] [ T928] [c0000011a7157cb0] [c0000011a7157cb0] __mutex_lock+0xf4/0x1050 [ 84.964436] [ T928] [c0000011a7157e00] [c000000000de21d8] pci_lock_rescan_remove+0x28/0x40 [ 84.964439] [ T928] [c0000011a7157e20] [c00000000004ed98] eeh_pe_bus_get+0x48/0xc0 [ 84.964442] [ T928] [c0000011a7157e50] [c00000 ---truncated---
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: powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling The recent commit 1010b4c012b0 ("powerpc/eeh: Make EEH driver device hotplug safe") restructured the EEH driver to improve synchronization with the PCI hotplug layer. However, it inadvertently moved pci_lock_rescan_remove() outside its intended scope in eeh_handle_normal_event(), leading to broken PCI error reporting and improper EEH event triggering. Specifically, eeh_handle_normal_event() acquired pci_lock_rescan_remove() before calling eeh_pe_bus_get(), but eeh_pe_bus_get() itself attempts to acquire the same lock internally, causing nested locking and disrupting normal EEH event handling paths. This patch adds a boolean parameter do_lock to _eeh_pe_bus_get(), with two public wrappers: eeh_pe_bus_get() with locking enabled. eeh_pe_bus_get_nolock() that skips locking. Callers that already hold pci_lock_rescan_remove() now use eeh_pe_bus_get_nolock() to avoid recursive lock acquisition. Additionally, pci_lock_rescan_remove() calls are restored to the correct position—after eeh_pe_bus_get() and immediately before iterating affected PEs and devices. This ensures EEH-triggered PCI removes occur under proper bus rescan locking without recursive lock contention. The eeh_pe_loc_get() function has been split into two functions: eeh_pe_loc_get(struct eeh_pe *pe) which retrieves the loc for given PE. eeh_pe_loc_get_bus(struct pci_bus *bus) which retrieves the location code for given bus. This resolves lockdep warnings such as: <snip> [ 84.964298] [ T928] ============================================ [ 84.964304] [ T928] WARNING: possible recursive locking detected [ 84.964311] [ T928] 6.18.0-rc3 #51 Not tainted [ 84.964315] [ T928] -------------------------------------------- [ 84.964320] [ T928] eehd/928 is trying to acquire lock: [ 84.964324] [ T928] c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964342] [ T928] but task is already holding lock: [ 84.964347] [ T928] c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964357] [ T928] other info that might help us debug this: [ 84.964363] [ T928] Possible unsafe locking scenario: [ 84.964367] [ T928] CPU0 [ 84.964370] [ T928] ---- [ 84.964373] [ T928] lock(pci_rescan_remove_lock); [ 84.964378] [ T928] lock(pci_rescan_remove_lock); [ 84.964383] [ T928] *** DEADLOCK *** [ 84.964388] [ T928] May be due to missing lock nesting notation [ 84.964393] [ T928] 1 lock held by eehd/928: [ 84.964397] [ T928] #0: c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964408] [ T928] stack backtrace: [ 84.964414] [ T928] CPU: 2 UID: 0 PID: 928 Comm: eehd Not tainted 6.18.0-rc3 #51 VOLUNTARY [ 84.964417] [ T928] Hardware name: IBM,9080-HEX POWER10 (architected) 0x800200 0xf000006 of:IBM,FW1060.00 (NH1060_022) hv:phyp pSeries [ 84.964419] [ T928] Call Trace: [ 84.964420] [ T928] [c0000011a7157990] [c000000001705de4] dump_stack_lvl+0xc8/0x130 (unreliable) [ 84.964424] [ T928] [c0000011a71579d0] [c0000000002f66e0] print_deadlock_bug+0x430/0x440 [ 84.964428] [ T928] [c0000011a7157a70] [c0000000002fd0c0] __lock_acquire+0x1530/0x2d80 [ 84.964431] [ T928] [c0000011a7157ba0] [c0000000002fea54] lock_acquire+0x144/0x410 [ 84.964433] [ T928] [c0000011a7157cb0] [c0000011a7157cb0] __mutex_lock+0xf4/0x1050 [ 84.964436] [ T928] [c0000011a7157e00] [c000000000de21d8] pci_lock_rescan_remove+0x28/0x40 [ 84.964439] [ T928] [c0000011a7157e20] [c00000000004ed98] eeh_pe_bus_get+0x48/0xc0 [ 84.964442] [ T928] [c0000011a7157e50] [c00000 ---truncated---

What

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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 control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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 → Uncontrolled Recursion → 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-674 ↗
CWE-674: Uncontrolled Recursion. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
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-674

Official authority intelligence

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

ENISA EUVD · EUVD-2026-32370Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

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

d?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=CVE-2026-45891 Référence CVE CVE-2026-45899 https://www.cve.org/CVERecord?id=CVE-2026-45899 Référence CVE CVE-2026-45902 https://www.cve.org/CVERecord?id=CVE-2026-45902 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45911 https://www.cve.org/CVERecord?id=CVE-2026-45911 Référence CVE CVE-2026-45912 https://www.cve.org/CVERecord?id=CVE-2026-45912 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45916 https://www.cve.org/CVERecord?id=CVE-2026-45916 Référence CVE CVE-2026-45919 https://www.cve.org/CVERecord?id=CVE-2026-45919 Référence CVE CVE-2026-45920 https://www.cve.org/CVERecord?id=CVE-2026-45920 Référence CVE CVE-2026-45924 https://www.cve.org/CVERecord?id=CVE-2026-45924 Référence CVE CVE-2026-45935 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-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43309 Référence CVE CVE-2026-43328 https://www.cve.org/CVERecord?id=CVE-2026-43328 Référence CVE CVE-2026-43352 https://www.cve.org/CVERecord?id=CVE-2026-43352 Référence CVE CVE-2026-43439 https://www.cve.org/CVERecord?id=CVE-2026-43439 Référence CVE CVE-2026-43440 https://www.cve.org/CVERecord?id=CVE-2026-43440 Référence CVE CVE-2026-43451 https://www.cve.org/CVERecord?id=CVE-2026-43451 Référence CVE CVE-2026-43475 https://www.cve.org/CVERecord?id=CVE-2026-43475 Référence CVE CVE-2026-45860 https://www.cve.org/CVERecord?id=CVE-2026-45860 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45905 https://www.cve.org/CVERecord?id=CVE-2026-45905 Référence CVE CVE-2026-45913 https://www.cve.org/CVERecord?id=CVE-2026-45913 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45917 https://www.cve.org/CVERecord?id=CVE-2026-45917 Référence CVE CVE-2026-45944 https://www.cve.org/CVERecord?id=CVE-2026-45944 Référence CVE CVE-2026-45973 https://www.cve.org/CVERecord?id=CVE-2026-45973 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

d?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45895 https://www.cve.org/CVERecord?id=CVE-2026-45895 Référence CVE CVE-2026-45900 https://www.cve.org/CVERecord?id=CVE-2026-45900 Référence CVE CVE-2026-45902 https://www.cve.org/CVERecord?id=CVE-2026-45902 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45905 https://www.cve.org/CVERecord?id=CVE-2026-45905 Référence CVE CVE-2026-45911 https://www.cve.org/CVERecord?id=CVE-2026-45911 Référence CVE CVE-2026-45913 https://www.cve.org/CVERecord?id=CVE-2026-45913 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45916 https://www.cve.org/CVERecord?id=CVE-2026-45916 Référence CVE CVE-2026-45917 https://www.cve.org/CVERecord?id=CVE-2026-45917 Référence CVE CVE-2026-45921 https://www.cve.org/CVERecord?id=CVE-2026-45921 Référence CVE CVE-2026-45923 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

d?id=CVE-2026-43466 Référence CVE CVE-2026-43475 https://www.cve.org/CVERecord?id=CVE-2026-43475 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-45857 https://www.cve.org/CVERecord?id=CVE-2026-45857 Référence CVE CVE-2026-45858 https://www.cve.org/CVERecord?id=CVE-2026-45858 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45899 https://www.cve.org/CVERecord?id=CVE-2026-45899 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45905 https://www.cve.org/CVERecord?id=CVE-2026-45905 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45917 https://www.cve.org/CVERecord?id=CVE-2026-45917 Référence CVE CVE-2026-45920 https://www.cve.org/CVERecord?id=CVE-2026-45920 Référence CVE CVE-2026-45923 https://www.cve.org/CVERecord?id=CVE-2026-45923 Référence CVE CVE-2026-45981 https://www.cve.org/CVERecord?id=CVE-2026-45981 Référence CVE CVE-2026-45985 https://www.cve.org/CVERecord?id=CVE-2026-45985 Référence CVE CVE-2026-45994 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-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=CVE-2026-45891 Référence CVE CVE-2026-45893 https://www.cve.org/CVERecord?id=CVE-2026-45893 Référence CVE CVE-2026-45895 https://www.cve.org/CVERecord?id=CVE-2026-45895 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45899 https://www.cve.org/CVERecord?id=CVE-2026-45899 Référence CVE CVE-2026-45902 https://www.cve.org/CVERecord?id=CVE-2026-45902 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45905 https://www.cve.org/CVERecord?id=CVE-2026-45905 Référence CVE CVE-2026-45910 https://www.cve.org/CVERecord?id=CVE-2026-45910 Référence CVE CVE-2026-45911 https://www.cve.org/CVERecord?id=CVE-2026-45911 Référence CVE CVE-2026-45912 https://www.cve.org/CVERecord?id=CVE-2026-45912 Référence CVE CVE-2026-45913 https://www.cve.org/CVERecord?id=CVE-2026-45913 Référence CVE CVE-2026-45914 https://www.cve.org/CVERecord?id=CVE-2026-45914 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45916 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-45875 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=CVE-2026-45891 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45899 https://www.cve.org/CVERecord?id=CVE-2026-45899 Référence CVE CVE-2026-45902 https://www.cve.org/CVERecord?id=CVE-2026-45902 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45911 https://www.cve.org/CVERecord?id=CVE-2026-45911 Référence CVE CVE-2026-45912 https://www.cve.org/CVERecord?id=CVE-2026-45912 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45916 https://www.cve.org/CVERecord?id=CVE-2026-45916 Référence CVE CVE-2026-45919 https://www.cve.org/CVERecord?id=CVE-2026-45919 Référence CVE CVE-2026-45920 https://www.cve.org/CVERecord?id=CVE-2026-45920 Référence CVE CVE-2026-45924 https://www.cve.org/CVERecord?id=CVE-2026-45924 Référence CVE CVE-2026-45935 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

d?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=CVE-2026-45891 Référence CVE CVE-2026-45893 https://www.cve.org/CVERecord?id=CVE-2026-45893 Référence CVE CVE-2026-45895 https://www.cve.org/CVERecord?id=CVE-2026-45895 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45902 https://www.cve.org/CVERecord?id=CVE-2026-45902 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45905 https://www.cve.org/CVERecord?id=CVE-2026-45905 Référence CVE CVE-2026-45910 https://www.cve.org/CVERecord?id=CVE-2026-45910 Référence CVE CVE-2026-45912 https://www.cve.org/CVERecord?id=CVE-2026-45912 Référence CVE CVE-2026-45913 https://www.cve.org/CVERecord?id=CVE-2026-45913 Référence CVE CVE-2026-45914 https://www.cve.org/CVERecord?id=CVE-2026-45914 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45916 https://www.cve.org/CVERecord?id=CVE-2026-45916 Référence CVE CVE-2026-45917 https://www.cve.org/CVERecord?id=

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-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45899 https://www.cve.org/CVERecord?id=CVE-2026-45899 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45912 https://www.cve.org/CVERecord?id=CVE-2026-45912 Référence CVE CVE-2026-45914 https://www.cve.org/CVERecord?id=CVE-2026-45914 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45916 https://www.cve.org/CVERecord?id=CVE-2026-45916 Référence CVE CVE-2026-45919 https://www.cve.org/CVERecord?id=CVE-2026-45919 Référence CVE CVE-2026-45920 https://www.cve.org/CVERecord?id=CVE-2026-45920 Référence CVE CVE-2026-45923 https://www.cve.org/CVERecord?id=CVE-2026-45923 Référence CVE CVE-2026-45936 https://www.cve.org/CVERecord?id=

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: SUSE Linux Micro Extras 6.2:kernel-obs-build
SUSE Linux Micro Extras 6.2:kernel-syms
SLES 15 SP1 CHOST Images for Amazon EC2
SLES 15 SP2 CHOST Images for Amazon EC2
SLES 15 SP3 CHOST Images for Amazon EC2
SLES 15 SP4 CHOST Images for Amazon EC2
SLES 15 SP5 CHOST Images for Amazon EC2
SLES 15 SP1 CHOST Images for Google
SLES 15 SP2 CHOST Images for Google
SLES 15 SP3 CHOST Images for Google
SLES 15 SP4 CHOST Images for Google
SLES 15 SP5 CHOST Images for Google
SLES 15 SP1 CHOST Images for Microsoft Azure
SLES 15 SP2 CHOST Images for Microsoft Azure
SLES 15 SP3 CHOST Images for Microsoft Azure
SLES 15 SP4 CHOST Images for Microsoft Azure
SLES 15 SP5 CHOST Images for Microsoft Azure
Fixed: Linux: < 6.17, 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.14 ≤ 6.18.*, 6.19.4 ≤ 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 27 May 2026 · Last source change 27 May 2026, 12:17 UTC · CWE-674 · Uncontrolled Recursion

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-32370

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceNIST NVD

NVD statusNVD enrichment underway

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-27CVE published

2026-05-27Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-32370↗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.

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling

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-32370

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication