Skip to main content

Linux Kernel CVE-2026-43344

| EUVDEUVD-2026-28628 MEDIUM
Reachable Assertion (CWE-617)
2026-05-08 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-m424-x6wr-wwgw
5.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local user access on Intel SPR/EMR server
  2. Delivery
    Boot system with NUMA disabled or offline UBOX-associated CPUs
  3. Exploit
    Trigger perf/uncore PCI enumeration (boot or module load)
  4. Execution
    uncore_device_to_die() returns -1 for all devices
  5. Persist
    WARN_ON_ONCE fires or PMON units silently dropped
  6. Impact
    Kernel warning/panic or hardware PMU rendered inoperative

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V16 - Security Logging and Error Handling Reachable assertion handling
Exploitation Conditions

Exploitation requires local authenticated access with at minimum low privileges (CVSS PR:L), confirmed by the AV:L/PR:L vector. The hardware prerequisite is an Intel Sapphire Rapids (SPR) or Emerald Rapids (EMR) server platform where the spr_update_device_location() code path is exercised during PCI enumeration. The PMON-loss bug is specifically triggered when NUMA is disabled in the Linux kernel on a NUMA-capable system (e.g., 'numa=off' boot parameter), causing pcibus_to_node() to return NUMA_NO_NODE. The WARN_ON_ONCE assertion path is triggered when uncore_device_to_die() returns -1 during the nr_node_ids > 8 scan, which occurs when all CPUs associated with a UBOX device are offline. Exploitation is limited to these conditions: local system access, Intel SPR/EMR hardware, and either NUMA-disabled boot configuration or offline CPU scenarios - not applicable to AMD platforms, non-server Intel hardware, or default NUMA-enabled configurations.

Impact

The CVSS 3.1 score of 5.5 (Medium) with vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H reflects local access with low privilege required - an authenticated local user must be able to interact with the perf subsystem or trigger PCI enumeration paths on affected hardware. The availability impact is rated High, consistent with a potential kernel crash via the reachable assertion or complete loss of hardware PMU functionality. EPSS at 0.02% (5th percentile) indicates very low automated exploitation probability, which aligns with the specialized hardware prerequisite (Intel SPR/EMR server platforms) and local access requirement. There is no CISA KEV listing and no public POC identified. The 'Information Disclosure' tag in EUVD metadata appears inconsistent with the CVSS C:N rating - it likely reflects the consequence of missing PMON visibility rather than data exfiltration, and should not be treated as a confirmed confidentiality impact. Real-world risk is primarily operational: server operators relying on Intel uncore performance counters for workload profiling or capacity planning may experience silent data loss or kernel instability, particularly on SPR/EMR deployments with NUMA disabled.

Exploit ScenarioDerived

A local unprivileged user on an Intel Sapphire Rapids server boots the system with NUMA disabled (e.g., 'numa=off' kernel parameter). When the perf subsystem initializes and spr_update_device_location() is called, uncore_device_to_die() returns -1 for all PCI devices, causing all PMON units to be silently skipped. On kernels where the WARN_ON_ONCE(die_id == -1) assertion path is reachable before the fix, the kernel may log a warning or, depending on panic_on_warn configuration, halt - resulting in a denial of service condition requiring physical or remote console access to recover. No public POC exists at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 18, 2026

Die ID initialization and lookup bugs in the Linux kernel's Intel uncore performance monitoring subsystem (perf/x86/intel/uncore) can cause a reachable assertion trigger or silent loss of PMON unit visibility on Intel Sapphire Rapids (SPR) and Emerald Rapids (EMR) server hardware. Authenticated local users on affected systems may crash the kernel via the WARN_ON_ONCE reachable assertion (CWE-617) or, when NUMA is disabled on a NUMA-capable platform, cause all uncore PMON units to be silently dropped from the RB tree - rendering hardware performance monitoring inoperative. No public exploit exists and EPSS is 0.02%, indicating no active exploitation pressure at time of analysis.

RemediationAI

Upstream fix commits are available at https://git.kernel.org/stable/c/6a5dc3ee97581da2907fc7acd62853f07184de67 (stable-6 tree, targeting the 6.19.14 patch release) and https://git.kernel.org/stable/c/a16d1ec4dd0cdcf689f324adde6067083bce9099 (mainline, targeting Linux 7.0). Administrators should update to Linux 6.19.14 or later in the stable series, or to Linux 7.0 once released, per vendor patch availability. Distribution-specific stable kernels (RHEL, SUSE, Ubuntu) should be monitored for backport availability. As an interim workaround on Intel SPR/EMR systems where NUMA is intentionally disabled, enabling NUMA in the kernel boot configuration (removing 'numa=off' or equivalent) will cause pcibus_to_node() to return valid node IDs, eliminating the -1 return path - however, this may alter memory allocation behavior and should be validated against workload requirements before deployment in production. No network-level mitigation is applicable given the local attack vector.

Affected VersionsENISA

Linux patch: 7.0
Linux 5.12
Linux patch: 6.19.14
Linux 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <6a5dc3ee97581da2907fc7acd62853f07184de67
Linux patch: 0
Linux 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <a16d1ec4dd0cdcf689f324adde6067083bce9099

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the Linux kernel's x86 Intel uncore driver (drivers/perf/x86/intel/uncore), which manages Performance Monitoring Units (PMUs) on Intel server platforms. The root cause (CWE-617, Reachable Assertion) involves two related logic bugs: first, snbep_pci2phy_map_init() incorrectly breaks out of the PCI device scan loop when uncore_device_to_die() returns -1 (indicating offline CPUs), causing subsequent UBOX devices to be silently skipped since pci_get_device() does not guarantee domain/bus order; second, when Linux NUMA support is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, driving uncore_device_to_die() to return -1 for all PCI devices, which in turn causes spr_update_device_location() - used for SPR and EMR - to omit all corresponding PMON units from the RB tree used for topology-aware PMU enumeration. The fix replaces uncore_device_to_die() with uncore_pcibus_to_dieid() in the NUMA-disabled path, leveraging the UBOX GIDNIDMAP register for topology resolution independent of Linux NUMA state. Affected CPEs include cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* with specific rc releases through 7.0-rc7.

Know when Intel gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM
Red Hat 5.5 LOW

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

3
CVSS changed
May 18, 2026 - 12:37 NVD
5.5 (MEDIUM)
Patch available
May 08, 2026 - 15:17 EUVD
CVE Published
May 08, 2026 - 14:16 nvd
UNKNOWN (no severity yet)

DescriptionNVD

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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Intel

View all
CVE-2021-44228 CRITICAL POC
10.0 Dec 10

Apache Log4j2 contains a critical JNDI injection vulnerability known as 'Log4Shell' that allows unauthenticated remote c

CVE-2017-5689 CRITICAL POC
9.8 May 02

An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Mana

CVE-2012-5958 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-0217 HIGH POC
7.2 Jun 12

The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and

CVE-2012-5959 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5964 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5963 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5961 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2017-5753 MEDIUM POC
5.6 Jan 04

Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of

CVE-2012-5965 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5962 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5960 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy