SecPod

Learn Search

Search across all Learn content

← Back to Security Research
Seven new Meltdown and Spectre-type CPU vulnerabilities that affect Intel, AMD, ARM CPUs

Seven new Meltdown and Spectre-type CPU vulnerabilities that affect Intel, AMD, ARM CPUs

Spectre and Meltdown vulnerabilities are one of the most significant known hardware vulnerabilities that affect the modern computer processors. Meltdown and Spectre vulnerabilities were exploited through malicious programs to retrieve secrets stored in the memory of other running programs, sensitive...

Dec 27, 2018By Ashwitha Kallalike3 min read

Spectre and Meltdown vulnerabilities are one of the most significant known hardware vulnerabilities that affect the modern computer processors. Meltdown and Spectre vulnerabilities were exploited through malicious programs to retrieve secrets stored in the memory of other running programs, sensitive information like passwords.

Both Spectre and Meltdown vulnerabilities make use of a feature in the processor chip known as “speculative execution“, a technique which used by most modern CPUs to optimize performance. A vulnerability scanning tool can detect these vulnerabilities.

Seven new variants of Spectre and Meltdown vulnerabilities

These are seven new transient execution attacks that discovered by the same team of Google Project Zero researchers, who discovered previous CPU vulnerabilities in the form of Meltdown (CVE-2017-5754) and Spectre (CVE-2017-5753 & CVE-2017-5715). Moreover, Intel, AMD, and ARM are the three processor vendors affect by these vulnerabilities. Among these seven processor vulnerabilities, two are Meltdown variants and other five are Spectre variants. However, a patch management tool can patch these vulnerabilities.

a. Meltdown-PK (Protection Key Bypass): Intel Skylake-SP server CPUs presently called Intel Xeon processor family supports memory-protection keys for user space. The access permissions of a page allowed to change directly from the user space through the memory protection keys and then an attacker can bypass both read/write isolation if he/she can control code execution over the process.

b. Meltdown-BR (Bounds Check Bypass): 32-bit processors in which out-of-bound array indices are encountered in hardware instructions that raise a bound range exceeded exception (BR). Sensitive information accessed after the out-of-bound exception using transient execution attack.

Spectre-PHT (Pattern History Table)

Branch predictor mistrained in the following four ways:

* Inside the same address space and the same branch location (same-address-space in-place mistraining)

* Within the same address space but with a different branch (same-address-space out-of-place)

* Inside an attacker controlled address space but with a branch at the same address as victim branch (cross-address-space in-place)

* Inside an attacker controlled address space at a agreed address to victim branch (cross-address-space out-of-place)

c. Spectre-PHT-CA-OP (Cross-Address-space Out of Place): Here the Pattern History table is used for exploiting the issue. It exploits within an attacker-controlled address space with an agreed address to the victim branch.

d. Spectre-PHT-SA-IP (Same Address-space In Place): This attack performed by performing Spectre-PHT attacks within the same address space and with a same branch location.

e. Spectre-PHT-SA-OP (Same Address-space Out of Place): This attack can be performed by performing Spectre-PHT attacks within the same address space but with a different branch location.

Spectre-BTB (Branch Target Buffer)

Branch Target Buffer, a register that used to storethepredicted destination of a branch in a processorusing branch prediction used for exploiting this vulnerability.

f. Spectre-BTB-SA-IP (Same Address-space In Place): The same address space and same branch location can be used to perform Spectre-BTB-SA-IP attack.

g. Spectre-BTB-SA-OP (Same Address-space Out of Place): The same address space with a different branch can be used to perform Spectre-BTB-SA-OP attack.

Defense for Spectre and Meltdown vulnerabilities:

However, according to the researchers who researched these issues, patches need hardware modifications exploited theoretically. As these issues need some changes to processor architecture and are not easy to patch in order to fully mitigate the vulnerabilities.

Also, to patch the other vulnerabilities, Meltdown (CVE-2017-5754) and Spectre (CVE-2017-5753 and CVE-2017-5715) , refer to  ‘Patching Meltdown and Spectre’:

Featured Posts

Open CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials
CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

CVE Research

CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

Two MikroTik RouterOS CVEs entered CISA KEV seven days after production fixes. Dated reporting places SSH-chain exploitation involving CVE-2026-86060 at least one calendar day before those releases; no comparable start date is established for CVE-2026-67277.

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch
Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

CVE Research

Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

Four vulnerabilities added to CISA’s KEV catalog on September 9, 2026 show widely different timelines between public disclosure and formal exploitation-based prioritization, ranging from one day to 239 days.

Sep 24, 2026

Open TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

CVE Research

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

A chronological look at how a long-running China-nexus espionage cluster evolved from server-side exploitation to a chained Chrome/Windows zero-day kit — and what that shift signals.

Sep 24, 2026