Vulnerability · Published Aug 15, 2026 · Assigned by Linux

CVE-2026-72154openrisc: Fix jump_label smp syncing

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 93.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: openrisc: Fix jump_label smp syncing The original commit 8c30b0018f9d ("openrisc: Add jump label support") copies from arm64 and does not properly consider how icache invalidation on remote cores works in OpenRISC. On OpenRISC remote icaches need to be invalidated otherwise static key's may remain state after updating. Fix SMP cache syncing by: 1. Properly invalidate remote core icaches on SMP systems by using icache_all_inv. The old code uses kick_all_cpus_sync() which runs a no-op IPI function call on remote CPU's which does execute a lot of code and flushes many cache lines in the process, but does not flush all and it's not correct on OpenRISC. 2. For architectures that do not have WRITETHROUGH caches be sure to flush the dcache after patching. To test this I first reproduced the issue using a custom test module [0]. The test confirmed that some icache lines maintained stale static_key code sequences after calling static_branch_enable(). After this patch there are no longer jump_label coherency issues. [0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.1.5-1DEBIAN-CVE-2026-72154
Ubuntu:26.04:LTSlinux7.0.0-38.38UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-aws7.0.0-1014.14UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-azure7.0.0-1017.17UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1016.16UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-gcp7.0.0-1014.14UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-gke7.0.0-1008.9UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-ibm7.0.0-1015.15UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2022.23UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1015.15UBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-oracle7.0.0-1013.13UBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-realtime7.0.0-38.38.1UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72154
Ubuntu:26.04:LTSlinux-riscv7.0.0-38.38.1UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-72154
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-38.38.1~24.04.1UBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-72154
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-72154

Affected products (as reported)

VendorProductVersions
Linux Linux 8c30b0018f9d93391573e091960d257fd9de120a – before 3fac46068fe4cea22ed373432b9173a915e8e60d8c30b0018f9d93391573e091960d257fd9de120a – before 57740658042daf591c57d6e700d9a304d59725528c30b0018f9d93391573e091960d257fd9de120a – before aca063c9024522e4e5b9a9d1927433f6a01785a3
Linux Linux 6.18

References