Bug 2141026 (CVE-2023-3006) - CVE-2023-3006 RHEL: Add Spectre-BHB mitigation for AmpereOne
Summary: CVE-2023-3006 RHEL: Add Spectre-BHB mitigation for AmpereOne
Alias: CVE-2023-3006
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 2211357
Blocks: 2140724 2140727 2141027
TreeView+ depends on / blocked
Reported: 2022-11-08 14:05 UTC by Sage McTaggart
Modified: 2023-06-07 14:27 UTC (History)
46 users (show)

Fixed In Version: Linux Kernel 6.1-rc1
Doc Type: If docs needed, set a value
Doc Text:
A known cache speculation vulnerability, the Branch History Injection (BHI) or Spectre-BHB, was found in new hw (that are cores Cortex: A57, A72, A76, A77, A78, A78AE, A78C, A710, X1, X2; Neoverse: N1, N2, V1; Ampere1). Spectre-BHB is similar to Spectre v2, except that malicious code uses the shared branch history (stored in the CPU Branch History Buffer, or BHB) to influence mispredicted branches within the victim's hardware context. Once that occurs, speculation caused by the mispredicted branches can cause cache allocation. This issue leads to information disclosure.
Clone Of:
Last Closed: 2023-05-16 20:48:25 UTC

Attachments (Terms of Use)

Description Sage McTaggart 2022-11-08 14:05:38 UTC
Description of problem:
Need Spectre-BHB mitigation added for new HW: Cortex: A57, A72, A76, A77, A78, A78AE, A78C, A710, X1, X2; Neoverse: N1, N2, V1; Ampere1.


Per AmpereOne erratum AC03_CPU_12, "Branch history may allow control of
speculative execution across software contexts," the AMPERE1 core needs the
bhb clearing loop to mitigate Spectre-BHB, with a loop iteration count of
And for the other listed hardware the fix is the same like for the AMPERE1 core.

For more information, read previous CVE-2022-23960 that is about Spectre-BHB too.


Comment 9 Alex 2023-05-31 08:31:51 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2211357]

Comment 12 Justin M. Forbes 2023-06-05 12:24:36 UTC
This was fixed for Fedora with the 6.0.7 stable kernel updates.

Note You need to log in before you can comment on or make changes to this bug.