CVE-2023-0045

Incorrect indirect branch prediction barrier in the Linux Kernel

HIGH
7.5
CVSS Score
Published: April 25, 2023 at 10:44 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
13 products affected across 3 vendorsLinux KernelDebian LinuxActive IQ Unified Manager

Using Linux Kernel by Linux?

Get instant alerts when new vulnerabilities affect Linux Kernel - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
PoC

Description

The current implementation of the prctl syscall does not issue an IBPB immediately during the syscall. The ib_prctl_set  function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL MSR on the function __speculation_ctrl_update, but the IBPB is only issued on the next schedule, when the TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to the prctl syscall.  The patch that added the support for the conditional mitigation via prctl (ib_prctl_set) dates back to the kernel 4.9.176. We recommend upgrading past commit a664ec9158eeddd75121d39c9a0758016097fa96

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.16.68 ≤ v < 3.174.14.86 ≤ v < 4.14.3034.19.7 ≤ v < 4.19.2704.20 ≤ v < 5.4.2294.4.180 ≤ v < 4.54.9.176 ≤ v < 4.105.11 ≤ v < 5.15.875.16 ≤ v < 6.0.195.5.0 ≤ v < 5.10.1636.1 ≤ v < 6.1.59137bb27e60e
Vendor states this is fixed in a664ec9158eeddd75121d39c9a0758016097fa96 (fixed)
Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.14.303, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.19.270, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.10.163, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.15.87, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.4.229, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.5, so it looks safe — our inference, not a vendor statement
All versions
netapp-h300s (same device)
All versions
netapp-h410c (same device)
All versions
netapp-h410s (same device)
All versions
netapp-h500s (same device)
All versions
netapp-h700s (same device)
All versions
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-610

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card