LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3665: System software utilizing Lazy FP state restore technique on systems using Intel Core-based microprocessors...

System software utilizing Lazy FP state restore technique on systems using Intel Core-based microprocessors may potentially allow a local process to infer data from another process through a speculative execution side channel.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-3665 is a processor-related information exposure risk tied to operating systems that used Lazy FP state restore on Intel Core-based systems. A local process may infer data from another process through speculative execution behavior. The issue matters most on shared hosts, multi-user servers, and virtualized environments where local code from different trust levels can run.

Executive priority

Treat this as a legacy platform and shared-host risk rather than an internet-facing emergency. Prioritize patch verification for virtualization hosts, multi-user servers, and appliances using affected kernels. The lack of KEV listing lowers urgency, but unsupported systems can preserve exposure for years.

Technical view

The CVE describes a speculative execution side channel involving Lazy FP state restore on Intel Core-based microprocessors. The affected condition is system software using that technique, not a remotely reachable service. Public references include Linux and FreeBSD security updates from Debian, Red Hat, Ubuntu, and FreeBSD. The bundle does not provide CVSS, CWE, or detailed product-version boundaries.

Likely exposure

Exposure is likely where Intel Core-based systems run operating systems or kernels that still use Lazy FP state restore. Modern, fully patched Linux and FreeBSD systems are less likely to remain exposed, but legacy, embedded, appliance, or unmaintained hosts need confirmation against vendor advisories.

Exploitation context

The source bundle supports a local-process information disclosure scenario, not remote compromise. KEV status is false, and no provided source states active exploitation. Exploitation would require the ability to run code locally or in a shared compute context and then infer data through a side channel.

Researcher notes

The record lacks CVSS, CWE, and detailed version ranges. The key exposure condition is OS use of Lazy FP state restore on Intel Core-based systems. Focus validation on kernel advisory coverage and whether the runtime environment permits attacker-controlled local code alongside sensitive workloads.

Mitigation direction

  • Apply relevant OS or kernel security updates from the system vendor.
  • Review Debian, Red Hat, Ubuntu, and FreeBSD advisories for affected release guidance.
  • Confirm Lazy FP state restore is disabled or remediated where vendor guidance names it.
  • Prioritize shared servers, virtualization hosts, and multi-user systems.
  • Check appliance vendor advisories before assuming kernel-level remediation is present.

Validation and detection

  • Inventory Intel Core-based systems and their operating system versions.
  • Compare kernel package levels against the cited vendor advisories.
  • Verify vendor documentation for Lazy FP state restore remediation status.
  • Review hypervisors and shared compute hosts before lower-risk endpoints.
  • Document unsupported systems that cannot receive vendor security updates.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-3665 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
23Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Intel CorporationIntel Core-based microprocessorsAllListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.