CVE-2024-10929
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn certain circumstances, an issue in Arm Cortex-A57, Cortex-A72 (revisions before r1p0), Cortex-A73 and Cortex-A75 may allow an adversary to gain a weak form of control over the victim's branch history.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA hardware vulnerability in specific Arm Cortex-A57, Cortex-A72 (revisions before r1p0), Cortex-A73 and Cortex-A75 processors allows an attacker in certain circumstances to exert weak control over a victim's branch history, potentially enabling speculative execution side-channel attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Arm processor modelRun 'lscpu' or 'cat /proc/cpuinfo' on Linux systems to determine the CPU model. Look for Cortex-A57, Cortex-A72, Cortex-A73, or Cortex-A75 in the output.Affected if The CPU is identified as an Arm Cortex-A57, Cortex-A72, Cortex-A73, or Cortex-A75 processor
-
Check Cortex-A72 revision numberFor Cortex-A72 systems specifically, examine the revision field in /proc/cpuinfo or via 'lscpu' output. Revisions are typically shown as r0p0, r1p0, etc.Affected if The revision is before r1p0 (e.g., r0p0) - note that this only applies to Cortex-A72; the other models are affected regardless of revision
-
Verify firmware/microcode update statusCheck system firmware version or microcode version if available. On Linux, this may be visible in 'dmesg' under CPU initialization messages, or via 'cat /sys/devices/system/cpu/microcode/version' if the interface exists.Affected if The system firmware/microcode has not been updated from the original baseline - vulnerable if no update has been applied to address this hardware flaw
-
Confirm speculative execution mitigation statusCheck for presence of branch predictor hardening or similar mitigations. On Linux, examine kernel command line parameters (cat /proc/cmdline) or check for Spectre/Meltdown mitigation status via 'cat /sys/kernel/debug/spectre_v2/status' if available.Affected if No OS-level speculative execution mitigations are present and the processor is one of the affected Cortex models listed above
A system is affected if it contains an Arm Cortex-A57, Cortex-A73, or Cortex-A75 processor of any revision, or a Cortex-A72 processor with revision before r1p0, and has not received firmware updates or OS-level mitigations to address the branch history manipulation flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply available processor microcode/firmware updates from Arm or device vendors. Where updates are unavailable, implement OS-level mitigations such as branch predictor hardening or consider replacing affected hardware with unaffected revisions.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10929 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data