Loading vulnerability…
CVE-2022-23960, also known as Spectre-BHB or Branch History Injection (BHI), is a speculative-execution side-channel vulnerability affecting certain Arm Cortex and Neoverse processors. It is related to Spectre v2. Attacker-controlled code can manipulate branch-history state shared through the Branch History Buffer (BHB), causing a victim execution context to speculatively follow mispredicted branches. Speculative execution may allocate cache state dependent on protected data, permitting that data to be inferred through cache-timing observations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
ARM64 Linux kernel mitigation issue for the Spectre-BHB speculative-execution vulnerability.
Spectre branch-history-buffer speculative-execution vulnerability affecting ARM64 systems.
A CPU speculative-execution side-channel vulnerability in which malicious code poisons shared branch-history state in the Branch History Buffer to induce victim-context branch mispredictions. Resulting speculative cache allocations may leak information that should be inaccessible.
An Arm CPU speculative-execution side-channel (Spectre-BHB) information disclosure vulnerability that can be abused to leak data from memory that should be inaccessible.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.