CVE-2026-72067

Description

A flaw was found in the Linux kernel's CPU hotplug mechanism. When the cpuhp_invoke_callback() function attempts to unwind previous operations after a failure, it can incorrectly reuse a return value. This issue allows a successful rollback to mask the original error, causing a failed CPU hotplug transition to appear as if it succeeded. This could lead to the system reporting an incorrect state for CPU hotplug operations.

Statement

This vulnerability is rated as Low severity because CPU hotplugging operations require administrative privileges, and the defect only results in masking an error during an aborted transition rather than enabling privilege escalation. Unprivileged local users cannot trigger or manipulate CPU state transitions directly. Consequently, this flaw has minimal security impact on standard Red Hat Enterprise Linux systems, primarily affecting internal state reporting during error unwinding.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity,Other

Technical Impact: Unexpected State; Alter Execution Logic

This weakness can lead to unpredictable behavior. If the function is used to make security-critical decisions or provide security-critical information, then the wrong status code can cause the product to assume that an action is safe or correct, even when it is not. This weakness could place the system in a state that could lead unexpected logic to be executed or other unintended behaviors.

Frequently Asked Questions

Want to get errata notifications? Sign up here.