Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.26% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-3006High confidence
A known cache speculation vulnerability, known as Branch History Injection (BHI) or Spectre-BHB, becomes actual again for the new hw AmpereOne
Unknown · Kernel
5.5MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 9 Jan 2025
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Kernel and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 11 affected or under-investigation product states without a fixed product state in the same current advisory
- Canonical Ubuntu Security: 1 affected package state with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.0.7-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.0.7-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.0.7-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.0.7-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi-realtime | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2023-3006 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityRHEL: Add Spectre-BHB mitigation for AmpereOne
The vendor explicitly identifies these products as affected by this CVE.
- bpftool as a component of Red Hat Enterprise Linux 8
- kernel as a component of Red Hat Enterprise Linux 8
- kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
- kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
- kernel-core as a component of Red Hat Enterprise Linux 8
- kernel-cross-headers as a component of Red Hat Enterprise Linux 8
- kernel-debug as a component of Red Hat Enterprise Linux 8
- kernel-debug-core as a component of Red Hat Enterprise Linux 8
- kernel-debug-devel as a component of Red Hat Enterprise Linux 8
- kernel-debug-modules as a component of Red Hat Enterprise Linux 8
- kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
- kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
- Summary
- 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.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
SSA-806742 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-806742: Multiple Vulnerabilities in SCALANCE XCM-/XRM-300 before V2.4
The vendor explicitly identifies these products as affected by this CVE.
- SCALANCE XCH328 (6GK5328-4TS01-2EC2)
- SCALANCE XCM324 (6GK5324-8TS01-2AC2)
- SCALANCE XCM328 (6GK5328-4TS01-2AC2)
- SCALANCE XCM332 (6GK5332-0GA01-2AC2)
- SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
- SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
- SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
- SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
- SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
- SCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)
- SCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)
- Summary
- A known cache speculation vulnerability, known as Branch History Injection (BHI) or Spectre-BHB, becomes actual again for the new hw AmpereOne. 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 obtaining information that should not be accessible.
- Remediation
- Update to V2.4 or later version
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
A known cache speculation vulnerability, known as Branch History Injection (BHI) or Spectre-BHB, becomes actual again for the new hw AmpereOne. 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 obtaining information that should not be accessible.
What
A known cache speculation vulnerability, known as Branch History Injection (BHI) or Spectre-BHB, becomes actual again for the new hw AmpereOne. 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 obtaining information that should not be accessible.
Why
The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or zeroize the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
A known cache speculation vulnerability, known as Branch History Injection (BHI) or Spectre-BHB, becomes actual again for the new hw AmpereOne. 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 obtaining information that should not be accessible.
Why
The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or zeroize the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Sensitive Information in Resource Not Removed Before Reuse → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-226 ↗
CWE-226: Sensitive Information in Resource Not Removed Before Reuse. The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or zeroize the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- bpftool as a component of Red Hat Enterprise Linux 8
- kernel as a component of Red Hat Enterprise Linux 8
- kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
- kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
- kernel-core as a component of Red Hat Enterprise Linux 8
- kernel-cross-headers as a component of Red Hat Enterprise Linux 8
- kernel-debug as a component of Red Hat Enterprise Linux 8
- kernel-debug-core as a component of Red Hat Enterprise Linux 8
- kernel-debug-devel as a component of Red Hat Enterprise Linux 8
- kernel-debug-modules as a component of Red Hat Enterprise Linux 8
- kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
- kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
- kernel-devel as a component of Red Hat Enterprise Linux 8
- kernel-doc as a component of Red Hat Enterprise Linux 8
- kernel-headers as a component of Red Hat Enterprise Linux 8
- kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8
- kernel-modules as a component of Red Hat Enterprise Linux 8
- kernel-modules-extra as a component of Red Hat Enterprise Linux 8
- kernel-modules-internal as a component of Red Hat Enterprise Linux 8
- kernel-rt as a component of Red Hat Enterprise Linux 8
- kernel-rt-core as a component of Red Hat Enterprise Linux 8
- kernel-rt-debug as a component of Red Hat Enterprise Linux 8
- kernel-rt-debug-core as a component of Red Hat Enterprise Linux 8
- kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 8
- kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 8
- kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 8
- kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 8
- kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 8
- kernel-rt-devel as a component of Red Hat Enterprise Linux 8
- kernel-rt-kvm as a component of Red Hat Enterprise Linux 8
- and 18 more
- Fixed
- bpftool-debuginfo-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- kernel-debug-debuginfo-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- kernel-debuginfo-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- kernel-debuginfo-common-x86_64-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- kernel-devel-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- kernel-tools-debuginfo-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- perf-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- perf-debuginfo-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- python3-perf-debuginfo-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Virtualization 4 Hypervisor for RHEL 8
- bpftool-0:4.18.0-372.105.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- bpftool-0:4.18.0-372.105.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- bpftool-0:4.18.0-372.105.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- bpftool-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- bpftool-debuginfo-0:4.18.0-372.105.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- bpftool-debuginfo-0:4.18.0-372.105.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- bpftool-debuginfo-0:4.18.0-372.105.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- bpftool-debuginfo-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-0:4.18.0-372.105.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-0:4.18.0-372.105.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-0:4.18.0-372.105.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-0:4.18.0-372.105.1.el8_6.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-abi-stablelists-0:4.18.0-372.105.1.el8_6.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-core-0:4.18.0-372.105.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-core-0:4.18.0-372.105.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-core-0:4.18.0-372.105.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-core-0:4.18.0-372.105.1.el8_6.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-debug-0:4.18.0-372.105.1.el8_6.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-debug-0:4.18.0-372.105.1.el8_6.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- kernel-debug-0:4.18.0-372.105.1.el8_6.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.6)
- and 99 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 31 May 2023 · Last source change 9 Jan 2025, 21:09 UTC · CWE-226 · Sensitive Information in Resource Not Removed Before Reuse
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-43699
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- Linux Kernel 6.1-rc1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- Linux Kernel 6.1-rc1 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.