Skip to content
Noroxi
CVE-2017-5715· NVD / CVE Program· CNA intel

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.

MediumCVSS 5.6 · v3.1—Proof of concept Fix available
Published
Jan 4, 2018
Updated
Jun 16, 2026
EPSS
74.0% · 99th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

44

Plan

Add it to your regular patch cycle.

CVSS
22 / 40 · 5.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
22 / 30 · 74.0%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
intelatom c
intelatom e
intelatom x3
intelatom x5-e3930
intelatom x5-e3940
intelatom x7-e3950
intelatom z
intelceleron j
intelceleron n
intelcore i3
intelcore i5
intelcore i7

and 188 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • intel atom cc2308
  • intel atom cc2316
  • intel atom cc2338
  • intel atom cc2350
  • intel atom cc2358
  • intel atom cc2508
  • intel atom cc2516
  • intel atom cc2518
  • intel atom cc2530
  • intel atom cc2538
  • intel atom cc2550
  • intel atom cc2558
  • intel atom cc2718
  • intel atom cc2730
  • intel atom cc2738
  • intel atom cc2750
  • intel atom cc2758
  • intel atom cc3308
  • intel atom cc3338
  • intel atom cc3508

Versions reported by the vendor

Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.

  • Intel Corporation Microprocessors with Speculative Execution

    • Allaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernelbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-corebefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-cross-headersbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-debugbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-debug-corebefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-debug-develbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-develbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-docbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-headersbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-modulesbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-modules-extrabefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-toolsbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-tools-libsbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8kernel-tools-libs-develbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8perfbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
AlmaLinux:8python3-perfbefore 4.18.0-372.9.1.el84.18.0-372.9.1.el8
Alpine:v3.5xenbefore 4.7.3-r44.7.3-r4
Alpine:v3.6xenbefore 4.8.2-r44.8.2-r4
Debian:12amd64-microcodebefore 3.20180515.13.20180515.1
Debian:12intel-microcodebefore 3.20180425.13.20180425.1

+96

Other highest-scoring records for the same primary product.

  • CVE-2017-5753Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an at
    50Plan
  • CVE-2017-5754Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information
    47Plan
  • CVE-2018-3639Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior mem
    40Plan
  • CVE-2018-3693Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an at
    25Monitor
  • CVE-2018-3640Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized d
    24Monitor
  • CVE-2018-9056Systems with microprocessors utilizing speculative execution may allow unauthorized disclosure of information to an attacker with local user
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:bpftool4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-372.9.1.el8 · AlmaLinux:8Package registry (OSV)
alpine:xen4.7.3-r4 · Alpine:v3.5Package registry (OSV)
debian:amd64-microcode3.20180515.1 · Debian:12Package registry (OSV)
debian:intel-microcode3.20180425.1 · Debian:12Package registry (OSV)
debian:linux4.15.11-1 · Debian:12Package registry (OSV)
debian:nvidia-graphics-drivers384.111-1 · Debian:12Package registry (OSV)
debian:qemu1:2.12~rc3+dfsg-1 · Debian:12Package registry (OSV)
debian:xen4.11.1~pre+1.733450b39b-1 · Debian:12Package registry (OSV)
opensuse:kernel-firmware20210901-1.2 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-amdgpu20250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-ath10k20250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-ath11k20250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-ath12k20250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-atheros20250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-bluetooth20250208-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-bnx220250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-brcm20250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-chelsio20250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-firmware-dpaa220250206-1.1 · openSUSE:TumbleweedPackage registry (OSV)

+25

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1
  • Proof-of-concept repository on GitHub ×5

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrylocal2018-01-03
Proof-of-concept repository on GitHubstars:542018-01-09
Proof-of-concept repository on GitHubstars:172018-01-14
Proof-of-concept repository on GitHubstars:02018-01-15
Proof-of-concept repository on GitHubstars:02024-05-06
Proof-of-concept repository on GitHubstars:02026-07-05

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-1 d
  2. Published
  3. TodaySep 30, 2026+3191 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records