Skip to content
Noroxi
CVE-2018-3640· NVD / CVE Program· CNA intel

Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized d

Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis, aka Rogue System Register Read (RSRE), Variant 3a.

MediumCVSS 5.6 · v3.0—No exploit Fix available
Published
May 22, 2018
Updated
Jun 16, 2026
EPSS
7.5% · 94th 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

24

Monitor

Low priority for now.

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

Affected systems

VendorProduct
intelatom c
intelatom e
intelatom z
intelceleron j
intelceleron n
intelcore i3
intelcore i5
intelcore i7
intelcore m
intelpentium
intelpentium j
intelpentium silver

and 187 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 cc3308
  • intel atom cc3338
  • intel atom cc3508
  • intel atom cc3538
  • intel atom cc3558
  • intel atom cc3708
  • intel atom cc3750
  • intel atom cc3758
  • intel atom cc3808
  • intel atom cc3830
  • intel atom cc3850
  • intel atom cc3858
  • intel atom cc3950
  • intel atom cc3955
  • intel atom cc3958
  • intel atom ee3805
  • intel atom ee3815
  • intel atom ee3825
  • intel atom ee3826

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 Multiple

    • Multipleaffected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12intel-microcodebefore 3.20180703.13.20180703.1
Debian:8intel-microcodebefore 3.20180703.2~deb8u13.20180703.2~deb8u1
Debian:9intel-microcodebefore 3.20180703.2~deb9u13.20180703.2~deb9u1
Debian:9intel-microcodebefore 3.20180807a.1~deb9u13.20180807a.1~deb9u1
openSUSE:Tumbleweedspectre-meltdown-checkerbefore 26.36.0602723-1.126.36.0602723-1.1
openSUSE:Tumbleweeducode-intelbefore 20210608-1.220210608-1.2
SUSE:Linux Enterprise Module for Basesystem 15ucode-intelbefore 20180807-3.6.120180807-3.6.1
SUSE:Linux Enterprise Module for Basesystem 15ucode-intelbefore 20180703-3.3.120180703-3.3.1
SUSE:Linux Enterprise Point of Sale 11 SP3microcode_ctlbefore 1.17-102.83.27.11.17-102.83.27.1
SUSE:Linux Enterprise Point of Sale 11 SP3microcode_ctlbefore 1.17-102.83.24.11.17-102.83.24.1
SUSE:OpenStack Cloud 7ucode-intelbefore 20180703-13.25.120180703-13.25.1
SUSE:OpenStack Cloud 7ucode-intelbefore 20180807-13.29.120180807-13.29.1

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-2017-5715Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information
    44Plan
  • 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-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
debian:intel-microcode3.20180703.1 · Debian:12Package registry (OSV)
opensuse:spectre-meltdown-checker26.36.0602723-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ucode-intel20210608-1.2 · openSUSE:TumbleweedPackage registry (OSV)
suse:microcode_ctl1.17-102.83.24.1 · SUSE:Linux Enterprise Point of Sale 11 SP3Package registry (OSV)
suse:ucode-intel20180703-3.3.1 · SUSE:Linux Enterprise Module for Basesystem 15Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

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.0/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