Cross-context data disclosure via branch-status eviction
Published Jan 22, 2025 · Updated Jul 22, 2025
Spectre-BSE in Arm Cortex-A57, Cortex-A72 before r1p0, Cortex-A73, and Cortex-A75 allows local users to influence victim branch history. Branch-status table entry eviction alters Branch History Buffer updates, induces target aliasing, and misdirects speculative indirect branches. Exploitation requires attacker code on an affected core and a suitable victim control-flow pattern; successful use exposes data across software contexts without altering architectural execution.
Summary
What happened
Spectre-BSE in Arm Cortex-A57, Cortex-A72 before r1p0, Cortex-A73, and Cortex-A75 allows local users to influence victim branch history. Branch-status table entry eviction alters Branch History Buffer updates, induces target aliasing, and misdirects speculative indirect branches. Exploitation requires attacker code on an affected core and a suitable victim control-flow pattern; successful use exposes data across software contexts without altering architectural execution.
The record
- CVE
- CVE-2024-10929
- Published
- Jan 22, 2025
- Updated
- Jul 22, 2025
- Vendor
- Arm
- Product
- Cortex-A73
- Classifications
- CWE-203, CWE-1423
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2025CVE publishedPublication date reported by the CVE source.
- Jul 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Spectre-BSE proof-of-concept artifactsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo