BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-43344High confidence

perf/x86/intel/uncore: Fix die ID init and look up bugs

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 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 14 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% 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

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

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

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.

25 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 21 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 releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.111-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.111-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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 feedCanonical 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-43344 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-43344
247 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix die ID init and look up bugs In snbep_pci2phy_map_init(), in the nr_node_ids > 8 path, uncore_device_to_die() may return -1 when all CPUs associated with the UBOX device are offline. Remove the WARN_ON_ONCE(die_id == -1) check for two reasons: - The current code breaks out of the loop. This is incorrect because pci_get_device() does not guarantee iteration in domain or bus order, so additional UBOX devices may be skipped during the scan. - Returning -EINVAL is incorrect, since marking offline buses with die_id == -1 is expected and should not be treated as an error. Separately, when NUMA is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die() to return -1 for all PCI devices. As a result, spr_update_device_location(), used on Intel SPR and EMR, ignores the corresponding PMON units and does not add them to the RB tree. Fix this by using uncore_pcibus_to_dieid(), which retrieves topology from the UBOX GIDNIDMAP register and works regardless of whether NUMA is enabled in Linux. This requires snbep_pci2phy_map_init() to be added in spr_uncore_pci_init(). Keep uncore_device_to_die() only for the nr_node_ids > 8 case, where NUMA is expected to be enabled.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-28628

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix die ID init and look up bugs In snbep_pci2phy_map_init(), in the nr_node_ids > 8 path, uncore_device_to_die() may return -1 when all CPUs associated with the UBOX device are offline. Remove the WARN_ON_ONCE(die_id == -1) check for two reasons: - The current code breaks out of the loop. This is incorrect because pci_get_device() does not guarantee iteration in domain or bus order, so additional UBOX devices may be skipped during the scan. - Returning -EINVAL is incorrect, since marking offline buses with die_id == -1 is expected and should not be treated as an error. Separately, when NUMA is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die() to return -1 for all PCI devices. As a result, spr_update_device_location(), used on Intel SPR and EMR, ignores the corresponding PMON units and does not add them to the RB tree. Fix this by using uncore_pcibus_to_dieid(), which retrieves topology from the UBOX GIDNIDMAP register and works regardless of whether NUMA is enabled in Linux. This requires snbep_pci2phy_map_init() to be added in spr_uncore_pci_init(). Keep uncore_device_to_die() only for the nr_node_ids > 8 case, where NUMA is expected to be enabled.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch 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 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix die ID init and look up bugs In snbep_pci2phy_map_init(), in the nr_node_ids > 8 path, uncore_device_to_die() may return -1 when all CPUs associated with the UBOX device are offline. Remove the WARN_ON_ONCE(die_id == -1) check for two reasons: - The current code breaks out of the loop. This is incorrect because pci_get_device() does not guarantee iteration in domain or bus order, so additional UBOX devices may be skipped during the scan. - Returning -EINVAL is incorrect, since marking offline buses with die_id == -1 is expected and should not be treated as an error. Separately, when NUMA is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die() to return -1 for all PCI devices. As a result, spr_update_device_location(), used on Intel SPR and EMR, ignores the corresponding PMON units and does not add them to the RB tree. Fix this by using uncore_pcibus_to_dieid(), which retrieves topology from the UBOX GIDNIDMAP register and works regardless of whether NUMA is enabled in Linux. This requires snbep_pci2phy_map_init() to be added in spr_uncore_pci_init(). Keep uncore_device_to_die() only for the nr_node_ids > 8 case, where NUMA is expected to be enabled.

What

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix die ID init and look up bugs In snbep_pci2phy_map_init(), in the nr_node_ids > 8 path, uncore_device_to_die() may return -1 when all CPUs associated with the UBOX device are offline. Remove the WARN_ON_ONCE(die_id == -1) check for two reasons: - The current code breaks out of the loop. This is incorrect because pci_get_device() does not guarantee iteration in domain or bus order, so additional UBOX devices may be skipped during the scan. - Returning -EINVAL is incorrect, since marking offline buses with die_id == -1 is expected and should not be treated as an error. Separately, when NUMA is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die() to return -1 for all PCI devices. As a result, spr_update_device_location(), used on Intel SPR and EMR, ignores the corresponding PMON units and does not add them to the RB tree. Fix this by using uncore_pcibus_to_dieid(), which retrieves topology from the UBOX GIDNIDMAP register and works regardless of whether NUMA is enabled in Linux. This requires snbep_pci2phy_map_init() to be added in spr_uncore_pci_init(). Keep uncore_device_to_die() only for the nr_node_ids > 8 case, where NUMA is expected to be enabled.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix die ID init and look up bugs In snbep_pci2phy_map_init(), in the nr_node_ids > 8 path, uncore_device_to_die() may return -1 when all CPUs associated with the UBOX device are offline. Remove the WARN_ON_ONCE(die_id == -1) check for two reasons: - The current code breaks out of the loop. This is incorrect because pci_get_device() does not guarantee iteration in domain or bus order, so additional UBOX devices may be skipped during the scan. - Returning -EINVAL is incorrect, since marking offline buses with die_id == -1 is expected and should not be treated as an error. Separately, when NUMA is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die() to return -1 for all PCI devices. As a result, spr_update_device_location(), used on Intel SPR and EMR, ignores the corresponding PMON units and does not add them to the RB tree. Fix this by using uncore_pcibus_to_dieid(), which retrieves topology from the UBOX GIDNIDMAP register and works regardless of whether NUMA is enabled in Linux. This requires snbep_pci2phy_map_init() to be added in spr_uncore_pci_init(). Keep uncore_device_to_die() only for the nr_node_ids > 8 case, where NUMA is expected to be enabled.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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.

02

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 → Reachable Assertion → 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-617 ↗

CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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-617
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-28628Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix die ID init and look up bugs In snbep_pci2phy_map_init(), in the nr_node_ids > 8 path, uncore_device_to_die() may return -1 when all CPUs associated with the UBOX device are offline. Remove the WARN_ON_ONCE(die_id == -1) check for two reasons: - The current code breaks out of the loop. This is incorrect because pci_get_device() does not guarantee iteration in domain or bus order, so additional UBOX devices may be skipped during the scan. - Returning -EINVAL is incorrect, since marking offline buses with die_id == -1 is expected and should not be treated as an error. Separately, when NUMA is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die() to return -1 for all PCI devices. As a result, spr_update_device_location(), used on Intel SPR and EMR, ignores the corresponding PMON units and does not add them to the RB tree. Fix this by using uncore_pcibus_to_dieid(), which retrieves topology from the UBOX GIDNIDMAP register and works regardless of whether NUMA is enabled in Linux. This requires snbep_pci2phy_map_init() to be added in spr_uncore_pci_init(). Keep uncore_device_to_die() only for the nr_node_ids > 8 case, where NUMA is expected to be enabled.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1454Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff 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-1253Multiples vulnérabilités dans le noyau Linux de Debian

025-40139 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2026-100070 https://www.cve.org/CVERecord?id=CVE-2026-100070 Référence CVE CVE-2026-100071 https://www.cve.org/CVERecord?id=CVE-2026-100071 Référence CVE CVE-2026-100075 https://www.cve.org/CVERecord?id=CVE-2026-100075 Référence CVE CVE-2026-100078 https://www.cve.org/CVERecord?id=CVE-2026-100078 Référence CVE CVE-2026-100079 https://www.cve.org/CVERecord?id=CVE-2026-100079 Référence CVE CVE-2026-23137 https://www.cve.org/CVERecord?id=CVE-2026-23137 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43344 https://www.cve.org/CVERecord?id=CVE-2026-43344 Référence CVE CVE-2026-45963 https://www.cve.org/CVERecord?id=CVE-2026-45963 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53102 https://www.cve.org/CVERecord?id=CVE-2026-53102 Référence CVE CVE-2026-53113 https://www.cve.org/CVERecord?id=CVE-2026-53113 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53313 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-43319 Référence CVE CVE-2026-43320 https://www.cve.org/CVERecord?id=CVE-2026-43320 Référence CVE CVE-2026-43324 https://www.cve.org/CVERecord?id=CVE-2026-43324 Référence CVE CVE-2026-43327 https://www.cve.org/CVERecord?id=CVE-2026-43327 Référence CVE CVE-2026-43330 https://www.cve.org/CVERecord?id=CVE-2026-43330 Référence CVE CVE-2026-43334 https://www.cve.org/CVERecord?id=CVE-2026-43334 Référence CVE CVE-2026-43340 https://www.cve.org/CVERecord?id=CVE-2026-43340 Référence CVE CVE-2026-43342 https://www.cve.org/CVERecord?id=CVE-2026-43342 Référence CVE CVE-2026-43343 https://www.cve.org/CVERecord?id=CVE-2026-43343 Référence CVE CVE-2026-43344 https://www.cve.org/CVERecord?id=CVE-2026-43344 Référence CVE CVE-2026-43346 https://www.cve.org/CVERecord?id=CVE-2026-43346 Référence CVE CVE-2026-43352 https://www.cve.org/CVERecord?id=CVE-2026-43352 Référence CVE CVE-2026-43353 https://www.cve.org/CVERecord?id=CVE-2026-43353 Référence CVE CVE-2026-43354 https://www.cve.org/CVERecord?id=CVE-2026-43354 Référence CVE CVE-2026-43357 https://www.cve.org/CVERecord?id=CVE-2026-43357 Référence CVE CVE-2026-43368 https://www.cve.org/CVERecord?id=CVE-2026-43368 Référence CVE CVE-2026-43370 https://www.cve.org/CVERecord?id=CVE-2026-43370 Référence CVE CVE-2026-43380 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-016385LinuxのLinux Kernelにおける到達可能なアサーションに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。perf/x86/intel/uncoreにおけるdie IDの初期化および検索のバグを修正しました。snbep_pci2phy_map_init()関数のnr_node_idsが8を超える経路において、すべてのCPUがオフラインである場合に、uncore_device_to_die()が-1を返すことがあります。WARN_ON_ONCE(die_id == -1)のチェックを削除した理由は2点あります。1点目は、現在のコードがループを途中で抜けてしまい、pci_get_device()がドメインやバスの順序での反復を保証しないため、スキャン中に追加のUBOXデバイスがスキップされる可能性があるからです。2点目は、-EINVALを返すのは誤りであり、die_id == -1でオフラインバスをマークすることは想定されており、エラーとして扱うべきではないからです。さらに、NUMAがNUMA対応プラットフォームで無効化されている場合において、pcibus_to_node()はNUMA_NO_NODEを返し、uncore_device_to_die()はすべてのPCIデバイスに対して-1を返します。その結果、Intel SPRおよびEMRで使用されるspr_update_device_location()は対応するPMONユニットを無視し、それらをRBツリーに追加しません。本問題は、UBOXのGIDNIDMAPレジスタからトポロジーを取得し、LinuxでNUMAが有効か無効かに関係なく動作するuncore_pcibus_to_dieid()を使用することで修正されました。これにより、snbep_pci2phy_map_init()をspr_uncore_pci_init()に追加する必要があります。uncore_device_to_die()は、NUMAが有効であることが期待されるnr_node_idsが8を超える場合のみに保持されます。

Official advisory ↗
03

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
Fixed
Linux: < 5.12, 6.6.157 ≤ 6.6.*, 6.12.109 ≤ 6.12.*, 6.18.50 ≤ 6.18.*, 6.19.14 ≤ 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.
04

Evidence and provenance

Published 8 May 2026 · Last source change 14 Sept 2026, 11:58 UTC · CWE-617 · Reachable Assertion

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-28628
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Linux: 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < bdb35811ff41a1678620a407056b6372f350028a, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < c79ef3342632e71ac8612a2a1cc17ac84dd258b4, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099, 5.12 · Fixed: Linux: < 5.12, 6.12.109 ≤ 6.12.*, 6.18.50 ≤ 6.18.*, 6.19.14 ≤ 6.19.*, 7.0 ≤ *
    After
    Linux: 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 184870af0e73f8ea2577c751fa098681465249f2, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < bdb35811ff41a1678620a407056b6372f350028a, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < c79ef3342632e71ac8612a2a1cc17ac84dd258b4, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099, 5.12 · Fixed: Linux: < 5.12, 6.6.157 ≤ 6.6.*, 6.12.109 ≤ 6.12.*, 6.18.50 ≤ 6.18.*, 6.19.14 ≤ 6.19.*, 7.0 ≤ *
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    Linux: 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099, 5.12 · Fixed: Linux: < 5.12, 6.19.14 ≤ 6.19.*, 7.0 ≤ *
    After
    Linux: 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < bdb35811ff41a1678620a407056b6372f350028a, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < c79ef3342632e71ac8612a2a1cc17ac84dd258b4, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099, 5.12 · Fixed: Linux: < 5.12, 6.12.109 ≤ 6.12.*, 6.18.50 ≤ 6.18.*, 6.19.14 ≤ 6.19.*, 7.0 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67; 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099; 5.12 · Fixed: < 5.12; 6.19.14 ≤ 6.19.*; 7.0 ≤ *
    After
    9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < bdb35811ff41a1678620a407056b6372f350028a; 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < c79ef3342632e71ac8612a2a1cc17ac84dd258b4; 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67; 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099; 5.12 · Fixed: < 5.12; 6.12.109 ≤ 6.12.*; 6.18.50 ≤ 6.18.*; 6.19.14 ≤ 6.19.*; 7.0 ≤ *
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < bdb35811ff41a1678620a407056b6372f350028a; 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < c79ef3342632e71ac8612a2a1cc17ac84dd258b4; 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67; 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099; 5.12 · Fixed: < 5.12; 6.12.109 ≤ 6.12.*; 6.18.50 ≤ 6.18.*; 6.19.14 ≤ 6.19.*; 7.0 ≤ *
    After
    Linux: 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < 6a5dc3ee97581da2907fc7acd62853f07184de67, 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 < a16d1ec4dd0cdcf689f324adde6067083bce9099, 5.12 · Fixed: Linux: < 5.12, 6.19.14 ≤ 6.19.*, 7.0 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-28628↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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.
Free version - for non-commercial use only.CVE-2026-43344 · cve.blacktree.nl