CVE-2026-72154
Description
A flaw was found in the Linux kernel, specifically within the OpenRISC architecture's handling of jump label synchronization in Symmetric Multiprocessing (SMP) systems. The implementation did not correctly invalidate instruction caches (icaches) on remote processor cores after updates. This oversight can lead to stale static key code sequences persisting in the icache, resulting in coherency issues and potentially incorrect program execution.
Statement
A moderate-severity flaw was found in the Linux kernel's OpenRISC architecture-specific jump label (static key) SMP synchronization code. When a static key is updated on an OpenRISC SMP system, the kernel relied on kick_all_cpus_sync(), which does not correctly invalidate the instruction caches (icaches) of remote CPU cores on OpenRISC. As a result, stale static key code sequences could persist in the icaches of remote cores, breaking instruction cache coherency and potentially causing incorrect kernel code execution, system instability, or denial of service. Red Hat rated this flaw Moderate severity with a CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), lower than the CVE.org score of 7.8, because Red Hat assessed the impact as limited to availability with no direct confidentiality or integrity impact. All Red Hat Enterprise Linux and Red Hat In-Vehicle OS kernel streams are marked NOT AFFECTED with the justification "Vulnerable Code not Present": the flawed jump label synchronization code is specific to the OpenRISC architecture, which is not present in the kernels Red Hat ships and supports.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
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,Confidentiality,Other
Technical Impact: Modify Application Data; Read Application Data; Alter Execution Logic; Unexpected State
If access to a shared resource is not correctly synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.