CINXE.COM

<!DOCTYPE html> <html class="client-nojs vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-sticky-header-enabled vector-toc-available" lang="en" dir="ltr"> <head> <meta charset="UTF-8"> <title>Meltdown (security vulnerability) - Wikipedia</title> <script>(function(){var className="client-js vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-sticky-header-enabled vector-toc-available";var cookie=document.cookie.match(/(?:^|; )enwikimwclientpreferences=([^;]+)/);if(cookie){cookie[1].split('%2C').forEach(function(pref){className=className.replace(new RegExp('(^| )'+pref.replace(/-clientpref-\w+$|[^\w-]+/g,'')+'-clientpref-\\w+( |$)'),'$1'+pref+'$2');});}document.documentElement.className=className;}());RLCONF={"wgBreakFrames":false,"wgSeparatorTransformTable":["",""],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy","wgMonthNames":["","January","February","March","April","May","June","July","August","September","October","November","December"],"wgRequestId":"af0f2ee6-37c5-4aab-b8c9-d71eb52ffe58","wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"Meltdown_(security_vulnerability)","wgTitle":"Meltdown (security vulnerability)","wgCurRevisionId":1265360095,"wgRevisionId":1265360095,"wgArticleId":56208586,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":null,"wgUserGroups":["*"],"wgCategories":["Articles with short description","Short description is different from Wikidata","Use dmy dates from June 2019","All articles with unsourced statements","Articles with unsourced statements from November 2020","Articles needing cleanup from January 2018","All pages needing cleanup","Articles with sections that need to be turned into prose from January 2018","All articles lacking reliable references","Articles lacking reliable references from January 2018","Intel x86 microprocessors","Transient execution CPU vulnerabilities","X86 memory management","2018 in computing"],"wgPageViewLanguage":"en","wgPageContentLanguage":"en","wgPageContentModel":"wikitext","wgRelevantPageName":"Meltdown_(security_vulnerability)","wgRelevantArticleId":56208586,"wgIsProbablyEditable":true,"wgRelevantPageIsProbablyEditable":true,"wgRestrictionEdit":[],"wgRestrictionMove":[],"wgNoticeProject":"wikipedia","wgCiteReferencePreviewsActive":false,"wgFlaggedRevsParams":{"tags":{"status":{"levels":1}}},"wgMediaViewerOnClick":true,"wgMediaViewerEnabledByDefault":true,"wgPopupsFlags":0,"wgVisualEditor":{"pageLanguageCode":"en","pageLanguageDir":"ltr","pageVariantFallbacks":"en"},"wgMFDisplayWikibaseDescriptions":{"search":true,"watchlist":true,"tagline":false,"nearby":true},"wgWMESchemaEditAttemptStepOversample":false,"wgWMEPageLength":90000,"wgEditSubmitButtonLabelPublish":true,"wgULSPosition":"interlanguage","wgULSisCompactLinksEnabled":false,"wgVector2022LanguageInHeader":true,"wgULSisLanguageSelectorEmpty":false,"wgWikibaseItemId":"Q47036859","wgCheckUserClientHintsHeadersJsApi":["brands","architecture","bitness","fullVersionList","mobile","model","platform","platformVersion"],"GEHomepageSuggestedEditsEnableTopics":true,"wgGETopicsMatchModeEnabled":false,"wgGELevelingUpEnabledForUser":false}; RLSTATE={"ext.globalCssJs.user.styles":"ready","site.styles":"ready","user.styles":"ready","ext.globalCssJs.user":"ready","user":"ready","user.options":"loading","ext.cite.styles":"ready","ext.pygments":"ready","skins.vector.search.codex.styles":"ready","skins.vector.styles":"ready","skins.vector.icons":"ready","jquery.makeCollapsible.styles":"ready","ext.wikimediamessages.styles":"ready","ext.visualEditor.desktopArticleTarget.noscript":"ready","ext.uls.interlanguage":"ready","wikibase.client.init":"ready"};RLPAGEMODULES=["ext.cite.ux-enhancements","ext.pygments.view","site","mediawiki.page.ready","jquery.makeCollapsible","mediawiki.toc","skins.vector.js","ext.centralNotice.geoIP","ext.centralNotice.startUp","ext.gadget.ReferenceTooltips","ext.gadget.switcher","ext.urlShortener.toolbar","ext.centralauth.centralautologin","mmv.bootstrap","ext.popups","ext.visualEditor.desktopArticleTarget.init","ext.visualEditor.targetLoader","ext.echo.centralauth","ext.eventLogging","ext.wikimediaEvents","ext.navigationTiming","ext.uls.interface","ext.cx.eventlogging.campaigns","ext.cx.uls.quick.actions","wikibase.client.vector-2022","ext.checkUser.clientHints","ext.quicksurveys.init","ext.growthExperiments.SuggestedEditSession"];</script> <script>(RLQ=window.RLQ||[]).push(function(){mw.loader.impl(function(){return["user.options@12s5i",function($,jQuery,require,module){mw.user.tokens.set({"patrolToken":"+\\","watchToken":"+\\","csrfToken":"+\\"}); }];});});</script> <link rel="stylesheet" href="/w/load.php?lang=en&modules=ext.cite.styles%7Cext.pygments%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediamessages.styles%7Cjquery.makeCollapsible.styles%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles%7Cwikibase.client.init&only=styles&skin=vector-2022"> <script async="" src="/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector-2022"></script> <meta name="ResourceLoaderDynamicStyles" content=""> <link rel="stylesheet" href="/w/load.php?lang=en&modules=site.styles&only=styles&skin=vector-2022"> <meta name="generator" content="MediaWiki 1.44.0-wmf.22"> <meta name="referrer" content="origin"> <meta name="referrer" content="origin-when-cross-origin"> <meta name="robots" content="max-image-preview:standard"> <meta name="format-detection" content="telephone=no"> <meta property="og:image" content="https://upload.wikimedia.org/wikipedia/commons/thumb/8/86/Meltdown_logo_with_text.svg/1200px-Meltdown_logo_with_text.svg.png"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="2334"> <meta property="og:image" content="https://upload.wikimedia.org/wikipedia/commons/thumb/8/86/Meltdown_logo_with_text.svg/800px-Meltdown_logo_with_text.svg.png"> <meta property="og:image:width" content="800"> <meta property="og:image:height" content="1556"> <meta property="og:image" content="https://upload.wikimedia.org/wikipedia/commons/thumb/8/86/Meltdown_logo_with_text.svg/640px-Meltdown_logo_with_text.svg.png"> <meta property="og:image:width" content="640"> <meta property="og:image:height" content="1245"> <meta name="viewport" content="width=1120"> <meta property="og:title" content="Meltdown (security vulnerability) - Wikipedia"> <meta property="og:type" content="website"> <link rel="preconnect" href="//upload.wikimedia.org"> <link rel="alternate" media="only screen and (max-width: 640px)" href="//en.m.wikipedia.org/wiki/Meltdown_(security_vulnerability)"> <link rel="alternate" type="application/x-wiki" title="Edit this page" href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit"> <link rel="apple-touch-icon" href="/static/apple-touch/wikipedia.png"> <link rel="icon" href="/static/favicon/wikipedia.ico"> <link rel="search" type="application/opensearchdescription+xml" href="/w/rest.php/v1/search" title="Wikipedia (en)"> <link rel="EditURI" type="application/rsd+xml" href="//en.wikipedia.org/w/api.php?action=rsd"> <link rel="canonical" href="https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)"> <link rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en"> <link rel="alternate" type="application/atom+xml" title="Wikipedia Atom feed" href="/w/index.php?title=Special:RecentChanges&feed=atom"> <link rel="dns-prefetch" href="//meta.wikimedia.org" /> <link rel="dns-prefetch" href="login.wikimedia.org"> </head> <body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject mw-editable page-Meltdown_security_vulnerability rootpage-Meltdown_security_vulnerability skin-vector-2022 action-view"><a class="mw-jump-link" href="#bodyContent">Jump to content</a> <div class="vector-header-container"> <header class="vector-header mw-header"> <div class="vector-header-start"> <nav class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-dropdown" class="vector-dropdown vector-main-menu-dropdown vector-button-flush-left vector-button-flush-right" title="Main menu" > <input type="checkbox" id="vector-main-menu-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-main-menu-dropdown" class="vector-dropdown-checkbox " aria-label="Main menu" > <label id="vector-main-menu-dropdown-label" for="vector-main-menu-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Main menu </label> <div class="vector-dropdown-content"> <div id="vector-main-menu-unpinned-container" class="vector-unpinned-container"> <div id="vector-main-menu" class="vector-main-menu vector-pinnable-element"> <div class="vector-pinnable-header vector-main-menu-pinnable-header vector-pinnable-header-unpinned" data-feature-name="main-menu-pinned" data-pinnable-element-id="vector-main-menu" data-pinned-container-id="vector-main-menu-pinned-container" data-unpinned-container-id="vector-main-menu-unpinned-container" > <div class="vector-pinnable-header-label">Main menu</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-main-menu.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-main-menu.unpin">hide</button> </div> <div id="p-navigation" class="vector-menu mw-portlet mw-portlet-navigation" > <div class="vector-menu-heading"> Navigation </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-mainpage-description" class="mw-list-item"><a href="/wiki/Main_Page" title="Visit the main page [z]" accesskey="z">Main page</a></li><li id="n-contents" class="mw-list-item"><a href="/wiki/Wikipedia:Contents" title="Guides to browsing Wikipedia">Contents</a></li><li id="n-currentevents" class="mw-list-item"><a href="/wiki/Portal:Current_events" title="Articles related to current events">Current events</a></li><li id="n-randompage" class="mw-list-item"><a href="/wiki/Special:Random" title="Visit a randomly selected article [x]" accesskey="x">Random article</a></li><li id="n-aboutsite" class="mw-list-item"><a href="/wiki/Wikipedia:About" title="Learn about Wikipedia and how it works">About Wikipedia</a></li><li id="n-contactpage" class="mw-list-item"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us" title="How to contact Wikipedia">Contact us</a></li> </ul> </div> </div> <div id="p-interaction" class="vector-menu mw-portlet mw-portlet-interaction" > <div class="vector-menu-heading"> Contribute </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-help" class="mw-list-item"><a href="/wiki/Help:Contents" title="Guidance on how to use and edit Wikipedia">Help</a></li><li id="n-introduction" class="mw-list-item"><a href="/wiki/Help:Introduction" title="Learn how to edit Wikipedia">Learn to edit</a></li><li id="n-portal" class="mw-list-item"><a href="/wiki/Wikipedia:Community_portal" title="The hub for editors">Community portal</a></li><li id="n-recentchanges" class="mw-list-item"><a href="/wiki/Special:RecentChanges" title="A list of recent changes to Wikipedia [r]" accesskey="r">Recent changes</a></li><li id="n-upload" class="mw-list-item"><a href="/wiki/Wikipedia:File_upload_wizard" title="Add images or other media for use on Wikipedia">Upload file</a></li><li id="n-specialpages" class="mw-list-item"><a href="/wiki/Special:SpecialPages">Special pages</a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> <a href="/wiki/Main_Page" class="mw-logo"> <img class="mw-logo-icon" src="/static/images/icons/wikipedia.png" alt="" aria-hidden="true" height="50" width="50"> <img class="mw-logo-wordmark" alt="Wikipedia" src="/static/images/mobile/copyright/wikipedia-wordmark-en.svg" style="width: 7.5em; height: 1.125em;"> <img class="mw-logo-tagline" alt="The Free Encyclopedia" src="/static/images/mobile/copyright/wikipedia-tagline-en.svg" width="117" height="13" style="width: 7.3125em; height: 0.8125em;"> </a> </div> <div class="vector-header-end"> <div id="p-search" role="search" class="vector-search-box-vue vector-search-box-collapses vector-search-box-show-thumbnail vector-search-box-auto-expand-width vector-search-box"> <a href="/wiki/Special:Search" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only search-toggle" title="Search Wikipedia [f]" accesskey="f"> Search </a> <div class="vector-typeahead-search-container"> <div class="cdx-typeahead-search cdx-typeahead-search--show-thumbnail cdx-typeahead-search--auto-expand-width"> <form action="/w/index.php" id="searchform" class="cdx-search-input cdx-search-input--has-end-button"> <div id="simpleSearch" class="cdx-search-input__input-wrapper" data-search-loc="header-moved"> <div class="cdx-text-input cdx-text-input--has-start-icon"> <input class="cdx-text-input__input" type="search" name="search" placeholder="Search Wikipedia" aria-label="Search Wikipedia" autocapitalize="sentences" title="Search Wikipedia [f]" accesskey="f" id="searchInput" > </div> <input type="hidden" name="title" value="Special:Search"> </div> <button class="cdx-button cdx-search-input__end-button">Search</button> </form> </div> </div> </div> <nav class="vector-user-links vector-user-links-wide" aria-label="Personal tools"> <div class="vector-user-links-main"> <div id="p-vector-user-menu-preferences" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-userpage" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-dropdown" class="vector-dropdown " title="Change the appearance of the page's font size, width, and color" > <input type="checkbox" id="vector-appearance-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-appearance-dropdown" class="vector-dropdown-checkbox " aria-label="Appearance" > <label id="vector-appearance-dropdown-label" for="vector-appearance-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Appearance </label> <div class="vector-dropdown-content"> <div id="vector-appearance-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <div id="p-vector-user-menu-notifications" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-overflow" class="vector-menu mw-portlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="https://donate.wikimedia.org/?wmf_source=donate&wmf_medium=sidebar&wmf_campaign=en.wikipedia.org&uselang=en" class="">Donate</a> </li> <li id="pt-createaccount-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:CreateAccount&returnto=Meltdown+%28security+vulnerability%29" title="You are encouraged to create an account and log in; however, it is not mandatory" class="">Create account</a> </li> <li id="pt-login-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:UserLogin&returnto=Meltdown+%28security+vulnerability%29" title="You're encouraged to log in; however, it's not mandatory. [o]" accesskey="o" class="">Log in</a> </li> </ul> </div> </div> </div> <div id="vector-user-links-dropdown" class="vector-dropdown vector-user-menu vector-button-flush-right vector-user-menu-logged-out" title="Log in and more options" > <input type="checkbox" id="vector-user-links-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-user-links-dropdown" class="vector-dropdown-checkbox " aria-label="Personal tools" > <label id="vector-user-links-dropdown-label" for="vector-user-links-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Personal tools </label> <div class="vector-dropdown-content"> <div id="p-personal" class="vector-menu mw-portlet mw-portlet-personal user-links-collapsible-item" title="User menu" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport" class="user-links-collapsible-item mw-list-item"><a href="https://donate.wikimedia.org/?wmf_source=donate&wmf_medium=sidebar&wmf_campaign=en.wikipedia.org&uselang=en">Donate</a></li><li id="pt-createaccount" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:CreateAccount&returnto=Meltdown+%28security+vulnerability%29" title="You are encouraged to create an account and log in; however, it is not mandatory"> Create account</a></li><li id="pt-login" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:UserLogin&returnto=Meltdown+%28security+vulnerability%29" title="You're encouraged to log in; however, it's not mandatory. [o]" accesskey="o"> Log in</a></li> </ul> </div> </div> <div id="p-user-menu-anon-editor" class="vector-menu mw-portlet mw-portlet-user-menu-anon-editor" > <div class="vector-menu-heading"> Pages for logged out editors <a href="/wiki/Help:Introduction" aria-label="Learn more about editing">learn more</a> </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-anoncontribs" class="mw-list-item"><a href="/wiki/Special:MyContributions" title="A list of edits made from this IP address [y]" accesskey="y">Contributions</a></li><li id="pt-anontalk" class="mw-list-item"><a href="/wiki/Special:MyTalk" title="Discussion about edits from this IP address [n]" accesskey="n">Talk</a></li> </ul> </div> </div> </div> </div> </nav> </div> </header> </div> <div class="mw-page-container"> <div class="mw-page-container-inner"> <div class="vector-sitenotice-container"> <div id="siteNotice"></div> </div> <div class="vector-column-start"> <div class="vector-main-menu-container"> <div id="mw-navigation"> <nav id="mw-panel" class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-pinned-container" class="vector-pinned-container"> </div> </nav> </div> </div> <div class="vector-sticky-pinned-container"> <nav id="mw-panel-toc" aria-label="Contents" data-event-name="ui.sidebar-toc" class="mw-table-of-contents-container vector-toc-landmark"> <div id="vector-toc-pinned-container" class="vector-pinned-container"> <div id="vector-toc" class="vector-toc vector-pinnable-element"> <div class="vector-pinnable-header vector-toc-pinnable-header vector-pinnable-header-pinned" data-feature-name="toc-pinned" data-pinnable-element-id="vector-toc" > <h2 class="vector-pinnable-header-label">Contents</h2> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-toc.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-toc.unpin">hide</button> </div> <ul class="vector-toc-contents" id="mw-panel-toc-list"> <li id="toc-mw-content-text" class="vector-toc-list-item vector-toc-level-1"> <a href="#" class="vector-toc-link"> <div class="vector-toc-text">(Top)</div> </a> </li> <li id="toc-Overview" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Overview"> <div class="vector-toc-text"> 1 Overview </div> </a> <ul id="toc-Overview-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-History" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#History"> <div class="vector-toc-text"> 2 History </div> </a> <ul id="toc-History-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Mechanism" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Mechanism"> <div class="vector-toc-text"> 3 Mechanism </div> </a> <button aria-controls="toc-Mechanism-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Mechanism subsection </button> <ul id="toc-Mechanism-sublist" class="vector-toc-list"> <li id="toc-Background_–_modern_CPU_design" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Background_–_modern_CPU_design"> <div class="vector-toc-text"> 3.1 Background – modern CPU design </div> </a> <ul id="toc-Background_–_modern_CPU_design-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Meltdown_exploit" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Meltdown_exploit"> <div class="vector-toc-text"> 3.2 Meltdown exploit </div> </a> <ul id="toc-Meltdown_exploit-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Impact" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Impact"> <div class="vector-toc-text"> 4 Impact </div> </a> <button aria-controls="toc-Impact-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Impact subsection </button> <ul id="toc-Impact-sublist" class="vector-toc-list"> <li id="toc-Affected_hardware" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Affected_hardware"> <div class="vector-toc-text"> 4.1 Affected hardware </div> </a> <ul id="toc-Affected_hardware-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Mitigation" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Mitigation"> <div class="vector-toc-text"> 5 Mitigation </div> </a> <ul id="toc-Mitigation-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-See_also" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#See_also"> <div class="vector-toc-text"> 6 See also </div> </a> <ul id="toc-See_also-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-References" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#References"> <div class="vector-toc-text"> 7 References </div> </a> <ul id="toc-References-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-External_links" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#External_links"> <div class="vector-toc-text"> 8 External links </div> </a> <ul id="toc-External_links-sublist" class="vector-toc-list"> </ul> </li> </ul> </div> </div> </nav> </div> </div> <div class="mw-content-container"> <main id="content" class="mw-body"> <header class="mw-body-header vector-page-titlebar"> <nav aria-label="Contents" class="vector-toc-landmark"> <div id="vector-page-titlebar-toc" class="vector-dropdown vector-page-titlebar-toc vector-button-flush-left" title="Table of Contents" > <input type="checkbox" id="vector-page-titlebar-toc-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-titlebar-toc" class="vector-dropdown-checkbox " aria-label="Toggle the table of contents" > <label id="vector-page-titlebar-toc-label" for="vector-page-titlebar-toc-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Toggle the table of contents </label> <div class="vector-dropdown-content"> <div id="vector-page-titlebar-toc-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <h1 id="firstHeading" class="firstHeading mw-first-heading">Meltdown (security vulnerability)</h1> <div id="p-lang-btn" class="vector-dropdown mw-portlet mw-portlet-lang" > <input type="checkbox" id="p-lang-btn-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-p-lang-btn" class="vector-dropdown-checkbox mw-interlanguage-selector" aria-label="Go to an article in another language. Available in 22 languages" > <label id="p-lang-btn-label" for="p-lang-btn-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--action-progressive mw-portlet-lang-heading-22" aria-hidden="true" > 22 languages </label> <div class="vector-dropdown-content"> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li class="interlanguage-link interwiki-ar mw-list-item"><a href="https://ar.wikipedia.org/wiki/%D9%85%D9%8A%D9%84%D8%AA%D8%AF%D8%A7%D9%88%D9%86" title="ميلتداون – Arabic" lang="ar" hreflang="ar" data-title="ميلتداون" data-language-autonym="العربية" data-language-local-name="Arabic" class="interlanguage-link-target">العربية</a></li><li class="interlanguage-link interwiki-ca mw-list-item"><a href="https://ca.wikipedia.org/wiki/Meltdown" title="Meltdown – Catalan" lang="ca" hreflang="ca" data-title="Meltdown" data-language-autonym="Català" data-language-local-name="Catalan" class="interlanguage-link-target">Català</a></li><li class="interlanguage-link interwiki-cs mw-list-item"><a href="https://cs.wikipedia.org/wiki/Meltdown_(zranitelnost)" title="Meltdown (zranitelnost) – Czech" lang="cs" hreflang="cs" data-title="Meltdown (zranitelnost)" data-language-autonym="Čeština" data-language-local-name="Czech" class="interlanguage-link-target">Čeština</a></li><li class="interlanguage-link interwiki-da mw-list-item"><a href="https://da.wikipedia.org/wiki/Meltdown_(it-sikkerhedss%C3%A5rbarhed)" title="Meltdown (it-sikkerhedssårbarhed) – Danish" lang="da" hreflang="da" data-title="Meltdown (it-sikkerhedssårbarhed)" data-language-autonym="Dansk" data-language-local-name="Danish" class="interlanguage-link-target">Dansk</a></li><li class="interlanguage-link interwiki-de mw-list-item"><a href="https://de.wikipedia.org/wiki/Meltdown_(Sicherheitsl%C3%BCcke)" title="Meltdown (Sicherheitslücke) – German" lang="de" hreflang="de" data-title="Meltdown (Sicherheitslücke)" data-language-autonym="Deutsch" data-language-local-name="German" class="interlanguage-link-target">Deutsch</a></li><li class="interlanguage-link interwiki-et mw-list-item"><a href="https://et.wikipedia.org/wiki/Meltdown" title="Meltdown – Estonian" lang="et" hreflang="et" data-title="Meltdown" data-language-autonym="Eesti" data-language-local-name="Estonian" class="interlanguage-link-target">Eesti</a></li><li class="interlanguage-link interwiki-es mw-list-item"><a href="https://es.wikipedia.org/wiki/Meltdown_(vulnerabilidad)" title="Meltdown (vulnerabilidad) – Spanish" lang="es" hreflang="es" data-title="Meltdown (vulnerabilidad)" data-language-autonym="Español" data-language-local-name="Spanish" class="interlanguage-link-target">Español</a></li><li class="interlanguage-link interwiki-fa mw-list-item"><a href="https://fa.wikipedia.org/wiki/%D9%85%D9%84%D8%AA%D8%AF%D8%A7%D9%88%D9%86_(%D8%A2%D8%B3%DB%8C%D8%A8%E2%80%8C%D9%BE%D8%B0%DB%8C%D8%B1%DB%8C_%D8%A7%D9%85%D9%86%DB%8C%D8%AA%DB%8C)" title="ملتداون (آسیب‌پذیری امنیتی) – Persian" lang="fa" hreflang="fa" data-title="ملتداون (آسیب‌پذیری امنیتی)" data-language-autonym="فارسی" data-language-local-name="Persian" class="interlanguage-link-target">فارسی</a></li><li class="interlanguage-link interwiki-fr mw-list-item"><a href="https://fr.wikipedia.org/wiki/Meltdown_(vuln%C3%A9rabilit%C3%A9)" title="Meltdown (vulnérabilité) – French" lang="fr" hreflang="fr" data-title="Meltdown (vulnérabilité)" data-language-autonym="Français" data-language-local-name="French" class="interlanguage-link-target">Français</a></li><li class="interlanguage-link interwiki-ko mw-list-item"><a href="https://ko.wikipedia.org/wiki/%EB%A9%9C%ED%8A%B8%EB%8B%A4%EC%9A%B4_(%EB%B2%84%EA%B7%B8)" title="멜트다운 (버그) – Korean" lang="ko" hreflang="ko" data-title="멜트다운 (버그)" data-language-autonym="한국어" data-language-local-name="Korean" class="interlanguage-link-target">한국어</a></li><li class="interlanguage-link interwiki-it mw-list-item"><a href="https://it.wikipedia.org/wiki/Meltdown_(vulnerabilit%C3%A0_di_sicurezza)" title="Meltdown (vulnerabilità di sicurezza) – Italian" lang="it" hreflang="it" data-title="Meltdown (vulnerabilità di sicurezza)" data-language-autonym="Italiano" data-language-local-name="Italian" class="interlanguage-link-target">Italiano</a></li><li class="interlanguage-link interwiki-lv mw-list-item"><a href="https://lv.wikipedia.org/wiki/Meltdown_(ievainojam%C4%ABba)" title="Meltdown (ievainojamība) – Latvian" lang="lv" hreflang="lv" data-title="Meltdown (ievainojamība)" data-language-autonym="Latviešu" data-language-local-name="Latvian" class="interlanguage-link-target">Latviešu</a></li><li class="interlanguage-link interwiki-lmo mw-list-item"><a href="https://lmo.wikipedia.org/wiki/Meltdown" title="Meltdown – Lombard" lang="lmo" hreflang="lmo" data-title="Meltdown" data-language-autonym="Lombard" data-language-local-name="Lombard" class="interlanguage-link-target">Lombard</a></li><li class="interlanguage-link interwiki-ml mw-list-item"><a href="https://ml.wikipedia.org/wiki/%E0%B4%AE%E0%B5%86%E0%B5%BD%E0%B4%B1%E0%B5%8D%E0%B4%B1%E0%B5%8D%E0%B4%A1%E0%B5%8C%E0%B5%BA_(%E0%B4%B8%E0%B5%81%E0%B4%B0%E0%B4%95%E0%B5%8D%E0%B4%B7%E0%B4%BE_%E0%B4%AA%E0%B4%BE%E0%B4%B3%E0%B4%BF%E0%B4%9A%E0%B5%8D%E0%B4%9A)" title="മെൽറ്റ്ഡൌൺ (സുരക്ഷാ പാളിച്ച) – Malayalam" lang="ml" hreflang="ml" data-title="മെൽറ്റ്ഡൌൺ (സുരക്ഷാ പാളിച്ച)" data-language-autonym="മലയാളം" data-language-local-name="Malayalam" class="interlanguage-link-target">മലയാളം</a></li><li class="interlanguage-link interwiki-nl mw-list-item"><a href="https://nl.wikipedia.org/wiki/Meltdown_(veiligheidslek)" title="Meltdown (veiligheidslek) – Dutch" lang="nl" hreflang="nl" data-title="Meltdown (veiligheidslek)" data-language-autonym="Nederlands" data-language-local-name="Dutch" class="interlanguage-link-target">Nederlands</a></li><li class="interlanguage-link interwiki-ja mw-list-item"><a href="https://ja.wikipedia.org/wiki/Meltdown" title="Meltdown – Japanese" lang="ja" hreflang="ja" data-title="Meltdown" data-language-autonym="日本語" data-language-local-name="Japanese" class="interlanguage-link-target">日本語</a></li><li class="interlanguage-link interwiki-pt mw-list-item"><a href="https://pt.wikipedia.org/wiki/Meltdown_(inform%C3%A1tica)" title="Meltdown (informática) – Portuguese" lang="pt" hreflang="pt" data-title="Meltdown (informática)" data-language-autonym="Português" data-language-local-name="Portuguese" class="interlanguage-link-target">Português</a></li><li class="interlanguage-link interwiki-ru mw-list-item"><a href="https://ru.wikipedia.org/wiki/Meltdown_(%D1%83%D1%8F%D0%B7%D0%B2%D0%B8%D0%BC%D0%BE%D1%81%D1%82%D1%8C)" title="Meltdown (уязвимость) – Russian" lang="ru" hreflang="ru" data-title="Meltdown (уязвимость)" data-language-autonym="Русский" data-language-local-name="Russian" class="interlanguage-link-target">Русский</a></li><li class="interlanguage-link interwiki-sk mw-list-item"><a href="https://sk.wikipedia.org/wiki/Meltdown_(zranite%C4%BEnos%C5%A5)" title="Meltdown (zraniteľnosť) – Slovak" lang="sk" hreflang="sk" data-title="Meltdown (zraniteľnosť)" data-language-autonym="Slovenčina" data-language-local-name="Slovak" class="interlanguage-link-target">Slovenčina</a></li><li class="interlanguage-link interwiki-sv mw-list-item"><a href="https://sv.wikipedia.org/wiki/Meltdown_(s%C3%A4kerhetsh%C3%A5l)" title="Meltdown (säkerhetshål) – Swedish" lang="sv" hreflang="sv" data-title="Meltdown (säkerhetshål)" data-language-autonym="Svenska" data-language-local-name="Swedish" class="interlanguage-link-target">Svenska</a></li><li class="interlanguage-link interwiki-uk mw-list-item"><a href="https://uk.wikipedia.org/wiki/Meltdown_(%D1%83%D1%80%D0%B0%D0%B7%D0%BB%D0%B8%D0%B2%D1%96%D1%81%D1%82%D1%8C)" title="Meltdown (уразливість) – Ukrainian" lang="uk" hreflang="uk" data-title="Meltdown (уразливість)" data-language-autonym="Українська" data-language-local-name="Ukrainian" class="interlanguage-link-target">Українська</a></li><li class="interlanguage-link interwiki-zh mw-list-item"><a href="https://zh.wikipedia.org/wiki/%E7%86%94%E6%AF%81_(%E5%AE%89%E5%85%A8%E6%BC%8F%E6%B4%9E)" title="熔毁 (安全漏洞) – Chinese" lang="zh" hreflang="zh" data-title="熔毁 (安全漏洞)" data-language-autonym="中文" data-language-local-name="Chinese" class="interlanguage-link-target">中文</a></li> </ul> <div class="after-portlet after-portlet-lang"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q47036859#sitelinks-wikipedia" title="Edit interlanguage links" class="wbc-editpage">Edit links</a></div> </div> </div> </div> </header> <div class="vector-page-toolbar"> <div class="vector-page-toolbar-container"> <div id="left-navigation"> <nav aria-label="Namespaces"> <div id="p-associated-pages" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-associated-pages" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-nstab-main" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/Meltdown_(security_vulnerability)" title="View the content page [c]" accesskey="c">Article</a></li><li id="ca-talk" class="vector-tab-noicon mw-list-item"><a href="/wiki/Talk:Meltdown_(security_vulnerability)" rel="discussion" title="Discuss improvements to the content page [t]" accesskey="t">Talk</a></li> </ul> </div> </div> <div id="vector-variants-dropdown" class="vector-dropdown emptyPortlet" > <input type="checkbox" id="vector-variants-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-variants-dropdown" class="vector-dropdown-checkbox " aria-label="Change language variant" > <label id="vector-variants-dropdown-label" for="vector-variants-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" >English </label> <div class="vector-dropdown-content"> <div id="p-variants" class="vector-menu mw-portlet mw-portlet-variants emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> </div> </div> </nav> </div> <div id="right-navigation" class="vector-collapsible"> <nav aria-label="Views"> <div id="p-views" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-views" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-view" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/Meltdown_(security_vulnerability)">Read</a></li><li id="ca-edit" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit" title="Edit this page [e]" accesskey="e">Edit</a></li><li id="ca-history" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=history" title="Past revisions of this page [h]" accesskey="h">View history</a></li> </ul> </div> </div> </nav> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-dropdown" class="vector-dropdown vector-page-tools-dropdown" > <input type="checkbox" id="vector-page-tools-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-tools-dropdown" class="vector-dropdown-checkbox " aria-label="Tools" > <label id="vector-page-tools-dropdown-label" for="vector-page-tools-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" >Tools </label> <div class="vector-dropdown-content"> <div id="vector-page-tools-unpinned-container" class="vector-unpinned-container"> <div id="vector-page-tools" class="vector-page-tools vector-pinnable-element"> <div class="vector-pinnable-header vector-page-tools-pinnable-header vector-pinnable-header-unpinned" data-feature-name="page-tools-pinned" data-pinnable-element-id="vector-page-tools" data-pinned-container-id="vector-page-tools-pinned-container" data-unpinned-container-id="vector-page-tools-unpinned-container" > <div class="vector-pinnable-header-label">Tools</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-page-tools.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-page-tools.unpin">hide</button> </div> <div id="p-cactions" class="vector-menu mw-portlet mw-portlet-cactions emptyPortlet vector-has-collapsible-items" title="More options" > <div class="vector-menu-heading"> Actions </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-more-view" class="selected vector-more-collapsible-item mw-list-item"><a href="/wiki/Meltdown_(security_vulnerability)">Read</a></li><li id="ca-more-edit" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit" title="Edit this page [e]" accesskey="e">Edit</a></li><li id="ca-more-history" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=history">View history</a></li> </ul> </div> </div> <div id="p-tb" class="vector-menu mw-portlet mw-portlet-tb" > <div class="vector-menu-heading"> General </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="t-whatlinkshere" class="mw-list-item"><a href="/wiki/Special:WhatLinksHere/Meltdown_(security_vulnerability)" title="List of all English Wikipedia pages containing links to this page [j]" accesskey="j">What links here</a></li><li id="t-recentchangeslinked" class="mw-list-item"><a href="/wiki/Special:RecentChangesLinked/Meltdown_(security_vulnerability)" rel="nofollow" title="Recent changes in pages linked from this page [k]" accesskey="k">Related changes</a></li><li id="t-upload" class="mw-list-item"><a href="//en.wikipedia.org/wiki/Wikipedia:File_Upload_Wizard" title="Upload files [u]" accesskey="u">Upload file</a></li><li id="t-permalink" class="mw-list-item"><a href="/w/index.php?title=Meltdown_(security_vulnerability)&oldid=1265360095" title="Permanent link to this revision of this page">Permanent link</a></li><li id="t-info" class="mw-list-item"><a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=info" title="More information about this page">Page information</a></li><li id="t-cite" class="mw-list-item"><a href="/w/index.php?title=Special:CiteThisPage&page=Meltdown_%28security_vulnerability%29&id=1265360095&wpFormIdentifier=titleform" title="Information on how to cite this page">Cite this page</a></li><li id="t-urlshortener" class="mw-list-item"><a href="/w/index.php?title=Special:UrlShortener&url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMeltdown_%28security_vulnerability%29">Get shortened URL</a></li><li id="t-urlshortener-qrcode" class="mw-list-item"><a href="/w/index.php?title=Special:QrCode&url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMeltdown_%28security_vulnerability%29">Download QR code</a></li> </ul> </div> </div> <div id="p-coll-print_export" class="vector-menu mw-portlet mw-portlet-coll-print_export" > <div class="vector-menu-heading"> Print/export </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="coll-download-as-rl" class="mw-list-item"><a href="/w/index.php?title=Special:DownloadAsPdf&page=Meltdown_%28security_vulnerability%29&action=show-download-screen" title="Download this page as a PDF file">Download as PDF</a></li><li id="t-print" class="mw-list-item"><a href="/w/index.php?title=Meltdown_(security_vulnerability)&printable=yes" title="Printable version of this page [p]" accesskey="p">Printable version</a></li> </ul> </div> </div> <div id="p-wikibase-otherprojects" class="vector-menu mw-portlet mw-portlet-wikibase-otherprojects" > <div class="vector-menu-heading"> In other projects </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="t-wikibase" class="wb-otherproject-link wb-otherproject-wikibase-dataitem mw-list-item"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q47036859" title="Structured data on this page hosted by Wikidata [g]" accesskey="g">Wikidata item</a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> </div> </div> </div> <div class="vector-column-end"> <div class="vector-sticky-pinned-container"> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-pinned-container" class="vector-pinned-container"> </div> </nav> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-pinned-container" class="vector-pinned-container"> <div id="vector-appearance" class="vector-appearance vector-pinnable-element"> <div class="vector-pinnable-header vector-appearance-pinnable-header vector-pinnable-header-pinned" data-feature-name="appearance-pinned" data-pinnable-element-id="vector-appearance" data-pinned-container-id="vector-appearance-pinned-container" data-unpinned-container-id="vector-appearance-unpinned-container" > <div class="vector-pinnable-header-label">Appearance</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-appearance.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-appearance.unpin">hide</button> </div> </div> </div> </nav> </div> </div> <div id="bodyContent" class="vector-body" aria-labelledby="firstHeading" data-mw-ve-target-container> <div class="vector-body-before-content"> <div class="mw-indicators"> </div> <div id="siteSub" class="noprint">From Wikipedia, the free encyclopedia</div> </div> <div id="contentSub"><div id="mw-content-subtitle"></div></div> <div id="mw-content-text" class="mw-body-content"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><div class="shortdescription nomobile noexcerpt noprint searchaux" style="display:none">Microprocessor security vulnerability</div> <style data-mw-deduplicate="TemplateStyles:r1236090951">.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}</style><div role="note" class="hatnote navigation-not-searchable">See also: <a href="/wiki/Speculative_execution_CPU_vulnerabilities" class="mw-redirect" title="Speculative execution CPU vulnerabilities">Speculative execution CPU vulnerabilities</a></div> <style data-mw-deduplicate="TemplateStyles:r1257001546">.mw-parser-output .infobox-subbox{padding:0;border:none;margin:-3px;width:auto;min-width:100%;font-size:100%;clear:none;float:none;background-color:transparent}.mw-parser-output .infobox-3cols-child{margin:auto}.mw-parser-output .infobox .navbar{font-size:100%}@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-full-data:not(.notheme) div:not(.notheme){background:#1f1f23!important;color:#f8f9fa}}@media(min-width:640px){body.skin--responsive .mw-parser-output .infobox-table{display:table!important}body.skin--responsive .mw-parser-output .infobox-table>caption{display:table-caption!important}body.skin--responsive .mw-parser-output .infobox-table>tbody{display:table-row-group}body.skin--responsive .mw-parser-output .infobox-table tr{display:table-row!important}body.skin--responsive .mw-parser-output .infobox-table th,body.skin--responsive .mw-parser-output .infobox-table td{padding-left:inherit;padding-right:inherit}}</style><table class="infobox"><caption class="infobox-title">Meltdown</caption><tbody><tr><td colspan="2" class="infobox-image"><a href="/wiki/File:Meltdown_logo_with_text.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/8/86/Meltdown_logo_with_text.svg/250px-Meltdown_logo_with_text.svg.png" decoding="async" width="150" height="292" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/8/86/Meltdown_logo_with_text.svg/330px-Meltdown_logo_with_text.svg.png 2x" data-file-width="512" data-file-height="996" /></a><div class="infobox-caption">The logo used by the team that discovered the vulnerability</div></td></tr><tr><th scope="row" class="infobox-label"><a href="/wiki/CVE_(identifier)" class="mw-redirect" title="CVE (identifier)">CVE identifier(s)</a></th><td class="infobox-data"><a href="/wiki/CVE_(identifier)" class="mw-redirect" title="CVE (identifier)">CVE</a>-<style data-mw-deduplicate="TemplateStyles:r1238218222">.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/6/65/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/d/d6/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/a/aa/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("//upload.wikimedia.org/wikipedia/commons/4/4c/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}</style><a rel="nofollow" class="external text" href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754">2017-5754</a></td></tr><tr><th scope="row" class="infobox-label">Date discovered</th><td class="infobox-data">January 2018; 7 years ago (2018-01)</td></tr><tr><th scope="row" class="infobox-label">Affected hardware</th><td class="infobox-data"><a href="/wiki/Intel_x86" class="mw-redirect" title="Intel x86">Intel x86</a> <a href="/wiki/Microprocessor" title="Microprocessor">microprocessors</a>, <a href="/wiki/IBM_Power_microprocessors" title="IBM Power microprocessors">IBM Power microprocessors</a>, and some <a href="/wiki/ARM_architecture_family" title="ARM architecture family">ARM</a>-based microprocessors</td></tr><tr><th scope="row" class="infobox-label">Website</th><td class="infobox-data"><a rel="nofollow" class="external text" href="https://meltdownattack.com">meltdownattack.com</a></td></tr></tbody></table> Meltdown is one of the two original <a href="/wiki/Speculative_execution_CPU_vulnerabilities" class="mw-redirect" title="Speculative execution CPU vulnerabilities">speculative execution CPU vulnerabilities</a> (the other being <a href="/wiki/Spectre_(security_vulnerability)" title="Spectre (security vulnerability)">Spectre</a>). Meltdown affects <a href="/wiki/List_of_Intel_processors" title="List of Intel processors">Intel x86 microprocessors</a>, <a href="/wiki/IBM_Power_microprocessors" title="IBM Power microprocessors">IBM Power microprocessors</a>,<a href="#cite_note-ibmpower-1">[1]</a> and some <a href="/wiki/List_of_ARM_processors" title="List of ARM processors">ARM-based microprocessors</a>.<a href="#cite_note-2">[2]</a><a href="#cite_note-auto1-3">[3]</a><a href="#cite_note-AT-20180105-4">[4]</a> It allows a rogue process to read all <a href="/wiki/Virtual_memory" title="Virtual memory">memory</a>, even when it is not authorized to do so. Meltdown affects a wide range of systems. At the time of disclosure (2018), this included all devices running any but the most recent and <a href="/wiki/Patch_(computing)" title="Patch (computing)">patched</a> versions of <a href="/wiki/IOS" title="IOS">iOS</a>,<a href="#cite_note-:1-5">[5]</a> <a href="/wiki/Linux" title="Linux">Linux</a>,<a href="#cite_note-6">[6]</a><a href="#cite_note-7">[7]</a> <a href="/wiki/MacOS" title="MacOS">macOS</a>,<a href="#cite_note-:1-5">[5]</a> or <a href="/wiki/Windows" class="mw-redirect" title="Windows">Windows</a>. Accordingly, many servers and <a href="/wiki/Cloud_service" class="mw-redirect" title="Cloud service">cloud services</a> were impacted,<a href="#cite_note-8">[8]</a> as well as a potential majority of <a href="/wiki/Smart_device" title="Smart device">smart devices</a> and <a href="/wiki/Embedded_device" class="mw-redirect" title="Embedded device">embedded devices</a> using ARM-based processors (mobile devices, smart TVs, printers and others), including a wide range of networking equipment. A purely software workaround to Meltdown has been assessed as slowing computers between 5 and 30 percent in certain specialized workloads,<a href="#cite_note-register-9">[9]</a> although companies responsible for software correction of the exploit reported minimal impact from general benchmark testing.<a href="#cite_note-10">[10]</a> Meltdown was issued a <a href="/wiki/Common_Vulnerabilities_and_Exposures" title="Common Vulnerabilities and Exposures">Common Vulnerabilities and Exposures</a> ID of <a href="/wiki/CVE_(identifier)" class="mw-redirect" title="CVE (identifier)">CVE</a>-<link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><a rel="nofollow" class="external text" href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754">2017-5754</a>, also known as Rogue Data Cache Load (RDCL),<a href="#cite_note-auto1-3">[3]</a> in January 2018. It was disclosed in conjunction with another exploit, <a href="/wiki/Spectre_(security_vulnerability)" title="Spectre (security vulnerability)">Spectre</a>, with which it shares some characteristics. The Meltdown and Spectre vulnerabilities are considered "catastrophic" by security analysts.<a href="#cite_note-11">[11]</a><a href="#cite_note-12">[12]</a><a href="#cite_note-13">[13]</a> The vulnerabilities are so severe that security researchers initially believed the reports to be false.<a href="#cite_note-14">[14]</a> Several procedures to help protect home computers and related devices from the Meltdown and Spectre security vulnerabilities have been published.<a href="#cite_note-NYT-20180104-15">[15]</a><a href="#cite_note-FM-20180105-16">[16]</a><a href="#cite_note-PCW-20180104-17">[17]</a><a href="#cite_note-CNET-20180104-18">[18]</a> Meltdown patches may produce performance loss.<a href="#cite_note-bbcflaw-19">[19]</a><a href="#cite_note-NYT-20180103-20">[20]</a><a href="#cite_note-TV-20180104-21">[21]</a> Spectre patches have been reported to significantly reduce performance, especially on older computers; on the then-newest (2017) <a href="/wiki/Coffee_Lake" title="Coffee Lake">eighth-generation Core</a> platforms, benchmark performance drops of 2–14 percent have been measured.<a href="#cite_note-PCW-20180109-22">[22]</a> On 18 January 2018, unwanted reboots, even for newer Intel chips, due to Meltdown and Spectre patches, were reported.<a href="#cite_note-ZDN-20180118-23">[23]</a> Nonetheless, according to <a href="/wiki/Dell" title="Dell">Dell</a>, "No 'real-world' exploits of these vulnerabilities [i.e., Meltdown and Spectre] have been reported to date [26 January 2018], though researchers have produced proof-of-concepts."<a href="#cite_note-DELL-20180126a-24">[24]</a><a href="#cite_note-DELL-20180126b-25">[25]</a> Dell further recommended "promptly adopting software updates, avoiding unrecognized hyperlinks and websites, not downloading files or applications from unknown sources ... following secure password protocols ... [using] security software to help protect against malware (advanced threat prevention software or anti-virus)."<a href="#cite_note-DELL-20180126a-24">[24]</a><a href="#cite_note-DELL-20180126b-25">[25]</a> On 15 March 2018, <a href="/wiki/Intel" title="Intel">Intel</a> reported that it would redesign its <a href="/wiki/Central_processing_unit" title="Central processing unit">CPUs</a> to help protect against the Meltdown and related Spectre vulnerabilities (especially, Meltdown and Spectre-V2, but not Spectre-V1), and expected to release the newly redesigned processors later in 2018.<a href="#cite_note-TVRG-20180315-26">[26]</a><a href="#cite_note-CNET-20180315-27">[27]</a><a href="#cite_note-AT-20180315-28">[28]</a><a href="#cite_note-TC-20180315-29">[29]</a> On 8 October 2018, Intel is reported to have added hardware and firmware mitigations regarding Spectre and Meltdown vulnerabilities to its latest processors.<a href="#cite_note-AT-20181008-30">[30]</a> <meta property="mw:PageProp/toc" /> <div class="mw-heading mw-heading2"><h2 id="Overview">Overview</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=1" title="Edit section: Overview">edit</a>]</div> Meltdown exploits a <a href="/wiki/Race_condition" title="Race condition">race condition</a>, inherent in the design of many modern <a href="/wiki/CPU" class="mw-redirect" title="CPU">CPUs</a>. This occurs between memory access and privilege checking during <a href="/wiki/Instruction_cycle" title="Instruction cycle">instruction</a> processing. Additionally, combined with a <a href="/wiki/Cache_side-channel_attack" class="mw-redirect" title="Cache side-channel attack">cache side-channel attack</a>, this vulnerability allows a process to bypass the normal privilege checks that isolate the exploit process from accessing data belonging to the <a href="/wiki/Operating_system" title="Operating system">operating system</a> and other running processes. The vulnerability allows an unauthorized process to read data from any address that is mapped to the current process's <a href="/wiki/Virtual_memory" title="Virtual memory">memory</a> space. Because the affected processors implement <a href="/wiki/Instruction_pipelining" title="Instruction pipelining">instruction pipelining</a>, the data from an unauthorized address will almost always be temporarily loaded into the <a href="/wiki/CPU_cache" title="CPU cache">CPU's cache</a> during <a href="/wiki/Out-of-order_execution" title="Out-of-order execution">out-of-order execution</a> – from which the data can be recovered. This can occur even if the original read instruction fails due to privilege checking, or if it never produces a readable result.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>] Since many <a href="/wiki/Operating_system" title="Operating system">operating systems</a> <a href="/wiki/Virtual_memory" title="Virtual memory">map</a> physical memory, <a href="/wiki/Kernel_(operating_system)" title="Kernel (operating system)">kernel</a> processes, and other running <a href="/wiki/User_space" class="mw-redirect" title="User space">user space</a> processes into the address space of every process, Meltdown effectively makes it possible for a rogue process to read any physical, kernel or other processes' mapped memory – regardless of whether it should be able to do so. Defenses against Meltdown would require avoiding the use of memory mapping in a manner vulnerable to such exploits (i.e. a software-based solution) or avoidance of the underlying race condition (i.e. a modification to the CPUs' <a href="/wiki/Microcode" title="Microcode">microcode</a> or execution path).[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>] The vulnerability is viable on any operating system in which privileged data is mapped into virtual memory for unprivileged processes – which includes many present-day operating systems. Meltdown could potentially impact a wider range of computers than presently identified, as there is little to no variation in the microprocessor families used by these computers.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>] A Meltdown attack cannot be detected if it is carried out, as it does not leave any traces in traditional log files.<a href="#cite_note-spectreattack.com-31">[31]</a><a href="#cite_note-32">[32]</a> <div class="mw-heading mw-heading2"><h2 id="History">History</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=2" title="Edit section: History">edit</a>]</div> <style data-mw-deduplicate="TemplateStyles:r1251242444">.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}</style><table class="box-Prose plainlinks metadata ambox ambox-style ambox-Prose" role="presentation"><tbody><tr><td class="mbox-image"><div class="mbox-image-div"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/f/f2/Edit-clear.svg/40px-Edit-clear.svg.png" decoding="async" width="40" height="40" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/f/f2/Edit-clear.svg/60px-Edit-clear.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/f/f2/Edit-clear.svg/80px-Edit-clear.svg.png 2x" data-file-width="48" data-file-height="48" /></div></td><td class="mbox-text"><div class="mbox-text-span">This section is in <a href="/wiki/MOS:LIST" class="mw-redirect" title="MOS:LIST">list</a> format but may read better as <a href="/wiki/MOS:PROSE" class="mw-redirect" title="MOS:PROSE">prose</a>. You can help by <a class="external text" href="https://en.wikipedia.org/w/index.php?title=Meltdown_(security_vulnerability)&action=edit">converting this section</a>, if appropriate. <a href="/wiki/Help:Editing" title="Help:Editing">Editing help</a> is available. (January 2018)</div></td></tr></tbody></table> Meltdown was discovered independently by Jann Horn from <a href="/wiki/Google" title="Google">Google</a>'s <a href="/wiki/Project_Zero_(Google)" class="mw-redirect" title="Project Zero (Google)">Project Zero</a>, Werner Haas and Thomas Prescher from Cyberus Technology, and Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from <a href="/wiki/Graz_University_of_Technology" title="Graz University of Technology">Graz University of Technology</a>.<a href="#cite_note-meltdownwebsite-33">[33]</a> The same research teams that discovered Meltdown also discovered Spectre. The security vulnerability was called Meltdown because "the vulnerability basically melts security boundaries which are normally enforced by the hardware".<a href="#cite_note-spectreattack.com-31">[31]</a> <ul><li>On 8 May 1995, a paper called "The Intel 80x86 Processor Architecture: Pitfalls for Secure Systems" published at the 1995 IEEE Symposium on Security and Privacy warned against a <a href="/wiki/Timing_channels" class="mw-redirect" title="Timing channels">covert timing channel</a> in the CPU cache and <a href="/wiki/Translation_lookaside_buffer" title="Translation lookaside buffer">translation lookaside buffer</a> (TLB).<a href="#cite_note-34">[34]</a> This analysis was performed under the auspices of the <a href="/wiki/National_Security_Agency" title="National Security Agency">National Security Agency</a>'s Trusted Products Evaluation Program (TPEP).</li> <li>In July 2012, Apple's <a href="/wiki/XNU" title="XNU">XNU</a> kernel (used in <a href="/wiki/MacOS" title="MacOS">macOS</a>, <a href="/wiki/IOS" title="IOS">iOS</a>, and <a href="/wiki/TvOS" title="TvOS">tvOS</a>, among others) adopted <a href="/wiki/Kernel_address_space_layout_randomization" class="mw-redirect" title="Kernel address space layout randomization">kernel address space layout randomization</a> (KASLR) with the release of <a href="/wiki/OS_X_Mountain_Lion" title="OS X Mountain Lion">OS X Mountain Lion</a> 10.8. In essence, the base of the system, including its kernel extensions (<a href="/wiki/Loadable_kernel_module" title="Loadable kernel module">kexts</a>) and memory zones, is randomly relocated during the boot process in an effort to reduce the operating system's vulnerability to attacks.<a href="#cite_note-35">[35]</a></li> <li>In March 2014, the <a href="/wiki/Linux" title="Linux">Linux</a> kernel adopted KASLR to mitigate address leaks.<a href="#cite_note-36">[36]</a></li> <li>On 8 August 2016, Anders Fogh and Daniel Gruss presented "Using Undocumented CPU Behavior to See Into Kernel Mode and Break KASLR in the Process" at the <a href="/wiki/Black_Hat_(conference)" class="mw-redirect" title="Black Hat (conference)">Black Hat</a> 2016 conference.<a href="#cite_note-37">[37]</a></li> <li>On 10 August 2016, Moritz Lipp et al. of Graz University of Technology published "ARMageddon: Cache Attacks on Mobile Devices" in the proceedings of the 25th <a href="/wiki/USENIX" title="USENIX">USENIX</a> security symposium. Even though focused on ARM, it laid the groundwork for the attack vector.<a href="#cite_note-38">[38]</a></li> <li>On 27 December 2016, at <a href="/wiki/33C3" class="mw-redirect" title="33C3">33C3</a>, Clémentine Maurice and Moritz Lipp of Graz University of Technology presented their talk "What could possibly go wrong with <insert x86 instruction here>? Side effects include side-channel attacks and bypassing kernel ASLR" which outlined already what was coming.<a href="#cite_note-39">[39]</a></li> <li>On 1 February 2017, the CVE numbers 2017–5715, 2017-5753 and 2017-5754 were assigned to Intel.</li> <li>On 27 February 2017, Bosman et al. of <a href="/wiki/Vrije_Universiteit_Amsterdam" title="Vrije Universiteit Amsterdam">Vrije Universiteit Amsterdam</a> published their findings of how <a href="/wiki/Address_space_layout_randomization" title="Address space layout randomization">address space layout randomization</a> (ASLR) could be abused on cache-based architectures at the NDSS Symposium.<a href="#cite_note-40">[40]</a></li> <li>On 27 March 2017, researchers at Graz University of Technology developed a proof-of-concept that could grab <a href="/wiki/RSA_(cryptosystem)" class="mw-redirect" title="RSA (cryptosystem)">RSA</a> keys from <a href="/wiki/Software_Guard_Extensions" title="Software Guard Extensions">Intel SGX</a> enclaves running on the same system within five minutes by using certain CPU instructions in lieu of a fine-grained timer to exploit <a href="/wiki/Cache_memory" class="mw-redirect" title="Cache memory">cache</a> <a href="/wiki/DRAM" class="mw-redirect" title="DRAM">DRAM</a> side-channels.<a href="#cite_note-41">[41]</a></li> <li>In June 2017, KASLR was found to have a large class of new vulnerabilities.<a href="#cite_note-42">[42]</a> Research at Graz University of Technology showed how to solve these vulnerabilities by preventing all access to unauthorized pages.<a href="#cite_note-43">[43]</a> A presentation on the resulting <a href="/wiki/KAISER" class="mw-redirect" title="KAISER">KAISER</a> technique was submitted for the Black Hat congress in July 2017, but was rejected by the organizers.<a href="#cite_note-Gruss_20180103-44">[44]</a> Nevertheless, this work led to <a href="/wiki/Kernel_page-table_isolation" title="Kernel page-table isolation">kernel page-table isolation</a> (KPTI, originally known as KAISER) in 2017, which was confirmed to eliminate a large class of security bugs, including some limited protection against the not-yet-discovered Meltdown – a fact confirmed by the Meltdown authors.<a href="#cite_note-MeltdownPaper-45">[45]</a></li> <li>In July 2017, research made public on the CyberWTF website by security researcher Anders Fogh outlined the use of a cache timing attack to read kernel space data by observing the results of speculative operations conditioned on data fetched with invalid privileges.<a href="#cite_note-46">[46]</a></li> <li>In October 2017, KASLR support on amd64 was added to NetBSD-current, making <a href="/wiki/NetBSD" title="NetBSD">NetBSD</a> the first totally open-source BSD system to support kernel address space layout randomization.<a href="#cite_note-47">[47]</a> However, the partially open-source<a href="#cite_note-48">[48]</a> <a href="/wiki/Darwin_(operating_system)" title="Darwin (operating system)">Apple Darwin</a>, which forms the foundation of macOS and iOS (among others), is based on <a href="/wiki/FreeBSD" title="FreeBSD">FreeBSD</a>; KASLR was added to its XNU kernel in 2012 as noted above.</li> <li>On 14 November 2017, security researcher Alex Ionescu publicly mentioned changes in the new version of Windows 10 that would cause some speed degradation without explaining the necessity for the changes, just referring to similar changes in Linux.<a href="#cite_note-Ionescu_20171114-49">[49]</a></li> <li>After affected hardware and software vendors had been made aware of the issue on 28 July 2017,<a href="#cite_note-Gibbs_20180104-50">[50]</a> the two vulnerabilities were made public jointly, on 3 January 2018, several days ahead of the coordinated release date of 9 January 2018 as news sites started reporting about commits to the Linux kernel and mails to its mailing list.<a href="#cite_note-register-9">[9]</a> As a result, patches were not available for some platforms, such as <a href="/wiki/Ubuntu_(operating_system)" class="mw-redirect" title="Ubuntu (operating system)">Ubuntu</a>,<a href="#cite_note-51">[51]</a> when the vulnerabilities were disclosed.</li> <li>On 28 January 2018, Intel was reported to have shared news of the Meltdown and Spectre security vulnerabilities with Chinese technology companies before notifying the U.S. government of the flaws.<a href="#cite_note-TC-20180128-52">[52]</a></li> <li>On 8 October 2018, Intel was reported to have added hardware and firmware mitigations regarding Spectre and Meltdown vulnerabilities to its latest processors.<a href="#cite_note-AT-20181008-30">[30]</a></li> <li>In November 2018, two new variants of the attacks were revealed. Researchers attempted to compromise CPU protection mechanisms using code to exploit weaknesses in memory protection and the <code class="mw-highlight mw-highlight-lang-text mw-content-ltr" style="" dir="ltr">BOUND</code> instruction. They also attempted but failed to exploit CPU operations for memory alignment, division by zero, supervisor modes, segment limits, invalid opcodes, and non-executable code.<a href="#cite_note-zdnet-nov2018-53">[53]</a></li></ul> <div class="mw-heading mw-heading2"><h2 id="Mechanism">Mechanism</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=3" title="Edit section: Mechanism">edit</a>]</div> Meltdown<a href="#cite_note-MeltdownPaper-45">[45]</a> relies on a <a href="/wiki/CPU" class="mw-redirect" title="CPU">CPU</a> <a href="/wiki/Race_condition" title="Race condition">race condition</a> that can arise between instruction execution and privilege checking. Put briefly, the instruction execution leaves side effects that constitute information not hidden to the process by the privilege check. The process carrying out Meltdown then uses these side effects to infer the values of <a href="/wiki/Virtual_memory" title="Virtual memory">memory mapped data</a>, bypassing the privilege check. The following provides an overview of the exploit, and the memory mapping that is its target. The attack is described in terms of an <a href="/wiki/Intel" title="Intel">Intel</a> processor running <a href="/wiki/Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> or <a href="/wiki/Linux" title="Linux">Linux</a>, the main test targets used in the original paper, but it also affects other processors and operating systems, including <a href="/wiki/MacOS" title="MacOS">macOS</a> (aka OS X), <a href="/wiki/IOS" title="IOS">iOS</a>, and <a href="/wiki/Android_(operating_system)" title="Android (operating system)">Android</a>.<a href="#cite_note-MeltdownPaper-45">[45]</a> <div class="mw-heading mw-heading3"><h3 id="Background_–_modern_CPU_design">Background – modern CPU design</h3>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=4" title="Edit section: Background – modern CPU design">edit</a>]</div> Modern <a href="/wiki/CPU" class="mw-redirect" title="CPU">computer processors</a> use a variety of techniques to gain high levels of efficiency. Four widely used features are particularly relevant to Meltdown: <ul><li><a href="/wiki/Virtual_memory" title="Virtual memory">Virtual (paged) memory</a>, also known as memory mapping – used to make memory access more efficient and to control which processes can access which areas of memory. <dl><dd>A modern computer usually runs many <a href="/wiki/Process_(computing)" title="Process (computing)">processes</a> in parallel. In an operating system such as <a href="/wiki/Windows" class="mw-redirect" title="Windows">Windows</a> or <a href="/wiki/Linux" title="Linux">Linux</a>, each process is given the impression that it alone has complete use of the computer's <a href="/wiki/RAM" class="mw-redirect" title="RAM">physical memory</a>, and may do with it as it likes. In reality it will be allocated memory to use from the physical memory, which acts as a "pool" of available memory, when it first tries to use any given memory address (by trying to read or write to it). This allows multiple processes, including the <a href="/wiki/Kernel_(operating_system)" title="Kernel (operating system)">kernel</a> or <a href="/wiki/Operating_system" title="Operating system">operating system</a> itself, to co-habit on the same system, but retain their individual activity and integrity without being affected by other running processes, and without being vulnerable to interference or unauthorized data leaks caused by a rogue process.</dd></dl></li> <li><a href="/wiki/Protection_ring" title="Protection ring">Privilege levels</a>, or protection domains – provide a means by which the <a href="/wiki/Operating_system" title="Operating system">operating system</a> can control which processes are authorized to read which areas of virtual memory. <dl><dd>As virtual memory permits a computer to refer to vastly more memory than it will ever physically contain, the system can be greatly sped up by "mapping" every process and their in-use memory – in effect all memory of all active processes – into every process's virtual memory. In some systems all physical memory is mapped as well, for further speed and efficiency. This is usually considered safe, because the operating system can rely on <a href="/wiki/Protection_ring" title="Protection ring">privilege controls</a> built into the processor itself, to limit which areas of memory any given process is permitted to access. An attempt to access authorized memory will immediately succeed, and an attempt to access unauthorized memory will cause an <a href="/wiki/Exception_handling" title="Exception handling">exception</a> and void the read instruction, which will fail. Either the calling process or the operating system directs what will happen if an attempt is made to read from unauthorized memory – typically it causes an error condition and the process that attempted to execute the read will be terminated. As unauthorized reads are usually not part of normal program execution, it is much faster to use this approach than to pause the process every time it executes some function that requires privileged memory to be accessed, to allow that memory to be mapped into a readable address space. If the operating system immediately suspends and terminates any process that attempts to access an unauthorized memory location, then the process will have tricked the processor into accessing only one illegal memory address for it, and probably not have time to analyze the side-effects and store the result. If the operating system allows the process to simply <a href="/wiki/Exception_handling" title="Exception handling">recover</a> from the <a href="/wiki/Access_violation" class="mw-redirect" title="Access violation">access violation</a> and continue, then the process can analyze the side-effects, store the result, and repeat the sequence millions of times per second, thereby uncovering thousands of bytes of privileged data per second.</dd></dl></li> <li><a href="/wiki/Instruction_pipelining" title="Instruction pipelining">Instruction pipelining</a> and <a href="/wiki/Speculative_execution" title="Speculative execution">speculative execution</a> – used to allow instructions to execute in the most efficient manner possible – if necessary allowing them to run out of order or in parallel across various processing units within the <a href="/wiki/CPU" class="mw-redirect" title="CPU">CPU</a> – so long as the outcome is correct. <dl><dd>Modern processors commonly contain numerous separate <a href="/wiki/Execution_unit" title="Execution unit">execution units</a>, and a <a href="/wiki/Scheduling_(computing)" title="Scheduling (computing)">scheduler</a> that decodes instructions and decides, at the time they are executed, the most efficient way to execute them. This might involve the decision that two instructions can execute at the same time, or even out of order, on different execution units (known as "instruction pipelining"). So long as the correct outcome is still achieved, this maximizes efficiency by keeping all of the processor's execution units in use as much as possible. Some instructions, such as <a href="/wiki/Branch_(computer_science)" title="Branch (computer science)">conditional branches</a>, will lead to one of two different outcomes, depending on a condition. For example, if a value is 0, it will take one action, and otherwise will take a different action. In some cases, the CPU may not yet know which branch to take. This may be because a value is uncached. Rather than wait to learn the correct option, the CPU may proceed immediately (speculative execution). If so, it can either guess the correct option (predictive execution) or even take both (eager execution). If it executes the incorrect option, the CPU will attempt to discard all effects of its incorrect guess. <style data-mw-deduplicate="TemplateStyles:r1033199720">.mw-parser-output div.crossreference{padding-left:0}</style><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951" />(See also: <a href="/wiki/Branch_predictor" title="Branch predictor">Branch predictor</a>)</dd></dl></li> <li><a href="/wiki/CPU_cache" title="CPU cache">CPU cache</a> – a modest amount of memory within the CPU used to ensure it can work at high speed, to speed up memory access, and to facilitate "intelligent" execution of instructions in an efficient manner. <dl><dd>From the perspective of a CPU, the computer's physical memory is slow to access. Also the instructions a CPU runs are very often repetitive, or access the same or similar memory numerous times. To maximize efficient use of the CPU's resources, modern CPUs often have a modest amount of very fast on-chip memory, known as <a href="/wiki/CPU_cache" title="CPU cache">CPU cache</a>. When data is accessed or an instruction is read from physical memory, a copy of that information is routinely saved in the CPU cache at the same time. If the CPU later needs the same instruction or memory contents again, it can obtain it with minimal delay from its own cache rather than waiting for a request related to physical memory to take place.</dd></dl></li></ul> <div class="mw-heading mw-heading3"><h3 id="Meltdown_exploit">Meltdown exploit</h3>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=5" title="Edit section: Meltdown exploit">edit</a>]</div> Ordinarily, the mechanisms described above are considered secure. They provide the basis for most modern operating systems and processors. Meltdown exploits the way these features interact to bypass the CPU's fundamental privilege controls and access privileged and sensitive data from the operating system and other processes. To understand Meltdown, consider the data that is mapped in virtual memory (much of which the process is not supposed to be able to access) and how the CPU responds when a process attempts to access unauthorized memory. The process is running on a vulnerable version of <a href="/wiki/Windows" class="mw-redirect" title="Windows">Windows</a>, <a href="/wiki/Linux" title="Linux">Linux</a>, or <a href="/wiki/MacOS" title="MacOS">macOS</a>, on a <a href="/wiki/64-bit" class="mw-redirect" title="64-bit">64-bit</a> processor of a vulnerable type.<a href="#cite_note-MeltdownPaper-45">[45]</a> This is a very common combination across almost all desktop computers, notebooks, laptops, servers and mobile devices. <ol><li>The CPU encounters an instruction accessing the value, A, at an address forbidden to the process by the virtual memory system and the privilege check. Because of speculative execution, the instruction is scheduled and dispatched to an execution unit. This execution unit then schedules both the privilege check and the memory access.</li> <li>The CPU encounters an instruction accessing address Base+A, with Base chosen by the attacker. This instruction is also scheduled and dispatched to an execution unit.</li> <li>The privilege check informs the execution unit that the address of the value, A, involved in the access is forbidden to the process (per the information stored by the virtual memory system), and thus the instruction should fail and subsequent instructions should have no effect. Because these instructions were speculatively executed, however, the data at Base+A may have been cached before the privilege check – and may not have been undone by the execution unit (or any other part of the CPU). If this is indeed the case, the mere act of caching constitutes a leak of information in and of itself. At this point, Meltdown intervenes.<a href="#cite_note-MeltdownPaper-45">[45]</a></li> <li>The process executes a <a href="/wiki/Timing_attack" title="Timing attack">timing attack</a> by executing instructions referencing memory operands directly. To be effective, the operands of these instructions must be at addresses which cover the possible address, Base+A, of the rejected instruction's operand. Because the data at the address referred to by the rejected instruction, Base+A, was cached nevertheless, an instruction referencing the same address directly will execute faster. The process can detect this timing difference and determine the address, Base+A, that was calculated for the rejected instruction – and thus determine the value A at the forbidden memory address.</li></ol> Meltdown uses this technique in sequence to read every address of interest at high speed, and depending on other running processes, the result may contain passwords, encryption data, and any other sensitive information, from any address of any process that exists in its memory map. In practice, because cache side-channel attacks are slow, it is faster to extract data one bit at a time (only 2 × 8 = 16 cache attacks needed to read a byte, rather than 256 steps if it tried to read all 8 bits at once). <div class="mw-heading mw-heading2"><h2 id="Impact">Impact</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=6" title="Edit section: Impact">edit</a>]</div> The impact of Meltdown depends on the design of the CPU, the design of the operating system (specifically how it uses memory paging), and the ability of a malicious party to get any code run on that system, as well as the value of any data it could read if able to execute. <ul><li><a href="/wiki/CPU" class="mw-redirect" title="CPU">CPU</a> – Many of the most widely used modern CPUs from the late 1990s until early 2018 have the required exploitable design. However, it is possible to mitigate it within CPU design. A CPU that could detect and avoid memory access for unprivileged instructions, or was not susceptible to cache timing attacks or similar probes, or removed cache entries upon non-privilege detection (and did not allow other processes to access them until authorized) as part of abandoning the instruction, would not be able to be exploited in this manner. Some observers consider that all software solutions will be "workarounds" and the only true solution is to update affected CPU designs and remove the underlying weakness.</li> <li><a href="/wiki/Operating_system" title="Operating system">Operating system</a> – Most of the widely used and general-purpose operating systems use privilege levels and virtual memory mapping as part of their design. Meltdown can access only those pages that are memory mapped so the impact will be greatest if all active memory and processes are memory mapped in every process and have the least impact if the operating system is designed so that almost nothing can be reached in this manner. An operating system might also be able to mitigate in software to an extent by ensuring that probe attempts of this kind will not reveal anything useful. Modern operating systems use memory mapping to increase speed so this could lead to performance loss.</li> <li><a href="/wiki/Virtual_machine" title="Virtual machine">Virtual machine</a> – A Meltdown attack cannot be used to break out of a virtual machine, i.e., in fully virtualized machines guest user space can still read from guest kernel space, but not from host kernel space.<a href="#cite_note-Galowicz_Jan_3_2018-54">[54]</a> The bug enables reading memory from address space represented by the same <a href="/wiki/Page_table" title="Page table">page table</a>, meaning the bug does not work between virtual tables. That is, guest-to-host page tables are unaffected, only guest-to-same-guest or host-to-host, and of course host-to-guest since the host can already access the guest pages. This means different VMs on the same fully virtualized <a href="/wiki/Hypervisor" title="Hypervisor">hypervisor</a> cannot access each other's data, but different users on the same guest instance can access each other's data.<a href="#cite_note-Wheeler_Jan_4_2018-55">[55]</a></li> <li><a href="/wiki/Embedded_device" class="mw-redirect" title="Embedded device">Embedded device</a> – Among the vulnerable chips are those designed by <a href="/wiki/ARM_Holdings" class="mw-redirect" title="ARM Holdings">ARM</a> and <a href="/wiki/Intel" title="Intel">Intel</a> designed for standalone and embedded devices, such as mobile phones, smart TVs, networking equipment, vehicles, hard drives, industrial control, and the like. As with all vulnerabilities, if a third party cannot run code on the device, its internal vulnerabilities remain unexploitable. For example, an ARM processor in a cellphone or <a href="/wiki/Internet_of_Things" class="mw-redirect" title="Internet of Things">Internet of Things</a> "smart" device may be vulnerable, but the same processor used in a device that cannot download and run new code, such as a kitchen appliance or hard drive controller, is believed to not be exploitable.<a href="#cite_note-56">[56]</a>[<a href="/wiki/Wikipedia:NOTRS" class="mw-redirect" title="Wikipedia:NOTRS">better source needed</a>]</li></ul> The specific impact depends on the implementation of the address translation mechanism in the OS and the underlying hardware architecture. The attack can reveal the content of any memory that is mapped into a user address space, even if otherwise protected. For example, before <a href="/wiki/Kernel_page-table_isolation" title="Kernel page-table isolation">kernel page-table isolation</a> was introduced, most versions of Linux mapped all physical memory into the address space of every user-space process; the mapped addresses are (mostly) protected, making them unreadable from user-space and accessible only when transitioned into the kernel. The existence of these mappings makes transitioning to and from the kernel faster, but is unsafe in the presence of the Meltdown vulnerability, as the contents of all physical memory (which may contain sensitive information such as passwords belonging to other processes or the kernel) can then be obtained via the above method by any unprivileged process from user-space. According to researchers, "every Intel processor that implements <a href="/wiki/Out-of-order_execution" title="Out-of-order execution">out-of-order execution</a> is potentially affected, which is effectively every processor since 1995 (except <a href="/wiki/Intel_Itanium" class="mw-redirect" title="Intel Itanium">Intel Itanium</a>, and <a href="/wiki/Intel_Atom" title="Intel Atom">Intel Atom</a> before 2013)."<a href="#cite_note-meltdownwebsite-33">[33]</a> Intel responded to the reported security vulnerabilities with an official statement.<a href="#cite_note-Intel-20180103-57">[57]</a> The vulnerability is expected to impact major <a href="/wiki/Cloud_provider" class="mw-redirect" title="Cloud provider">cloud providers</a>, such as <a href="/wiki/Amazon_Web_Services" title="Amazon Web Services">Amazon Web Services</a> (AWS)<a href="#cite_note-58">[58]</a> and <a href="/wiki/Google_Cloud_Platform" title="Google Cloud Platform">Google Cloud Platform</a>. Cloud providers allow users to execute programs on the same physical servers where sensitive data might be stored, and rely on safeguards provided by the CPU to prevent unauthorized access to the privileged memory locations where that data is stored, a feature that the Meltdown exploit circumvents. The original paper reports that <a href="/wiki/Paravirtualization" class="mw-redirect" title="Paravirtualization">paravirtualization</a> (<a href="/wiki/Xen" title="Xen">Xen</a>) and <a href="/wiki/Container_(virtualization)" class="mw-redirect" title="Container (virtualization)">containers</a> such as <a href="/wiki/Docker_(software)" title="Docker (software)">Docker</a>, <a href="/wiki/LXC" title="LXC">LXC</a>, and <a href="/wiki/OpenVZ" title="OpenVZ">OpenVZ</a>, are affected.<a href="#cite_note-Galowicz_Jan_3_2018-54">[54]</a><a href="#cite_note-MeltdownPaper-45">[45]</a> They report that the attack on a fully virtualized machine allows the guest user space to read from the guest kernel memory, but not read from the host kernel space. <div class="mw-heading mw-heading3"><h3 id="Affected_hardware">Affected hardware</h3>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=7" title="Edit section: Affected hardware">edit</a>]</div> The Meltdown vulnerability primarily affects <a href="/wiki/List_of_Intel_processors" title="List of Intel processors">Intel microprocessors</a>,<a href="#cite_note-59">[59]</a> but the <a href="/wiki/ARM_architecture_family" title="ARM architecture family">ARM</a> Cortex-A75<a href="#cite_note-ARM_Security_Update-60">[60]</a> and IBM's Power<a href="#cite_note-ibmpower-1">[1]</a> microprocessors are also affected. The vulnerability does not affect <a href="/wiki/List_of_AMD_microprocessors" class="mw-redirect" title="List of AMD microprocessors">AMD microprocessors</a>.<a href="#cite_note-NYT-20180103-20">[20]</a><a href="#cite_note-61">[61]</a><a href="#cite_note-auto-62">[62]</a><a href="#cite_note-63">[63]</a> When the effect of Meltdown was first made public, Intel countered that the flaws affect all processors,<a href="#cite_note-64">[64]</a> but AMD denied this, saying "we believe AMD processors are not susceptible due to our use of privilege level protections within paging architecture".<a href="#cite_note-65">[65]</a> Researchers have indicated that the Meltdown vulnerability is exclusive to Intel processors, while the Spectre vulnerability can possibly affect some <a href="/wiki/Intel" title="Intel">Intel</a>, <a href="/wiki/AMD" title="AMD">AMD</a>, and <a href="/wiki/ARM_architecture_family" title="ARM architecture family">ARM</a> processors.<a href="#cite_note-66">[66]</a><a href="#cite_note-67">[67]</a><a href="#cite_note-68">[68]</a><a href="#cite_note-69">[69]</a> However, <a href="/wiki/Arm_Holdings" title="Arm Holdings">ARM</a> announced that some of their processors were vulnerable to Meltdown.<a href="#cite_note-ARM_Security_Update-60">[60]</a> Google has reported that any Intel processor since 1995 with out-of-order execution is potentially vulnerable to the Meltdown vulnerability (this excludes <a href="/wiki/Itanium" title="Itanium">Itanium</a> and pre-2013 <a href="/wiki/Intel_Atom" title="Intel Atom">Intel Atom</a> CPUs).<a href="#cite_note-70">[70]</a> Intel introduced speculative execution to their processors with Intel's <a href="/wiki/P6_(microarchitecture)" title="P6 (microarchitecture)">P6</a> family microarchitecture with the <a href="/wiki/Pentium_Pro" title="Pentium Pro">Pentium Pro</a> <a href="/wiki/IA-32" title="IA-32">IA-32</a> microprocessor in 1995.<a href="#cite_note-71">[71]</a> ARM has reported that the majority of their processors are not vulnerable, and published a list of the specific processors that are affected. The <a href="/wiki/ARM_Cortex-A75" title="ARM Cortex-A75">ARM Cortex-A75</a> core is affected directly by both Meltdown and Spectre vulnerabilities, and <a href="/wiki/ARM_Cortex-R7" class="mw-redirect" title="ARM Cortex-R7">Cortex-R7</a>, <a href="/wiki/ARM_Cortex-R8" class="mw-redirect" title="ARM Cortex-R8">Cortex-R8</a>, <a href="/wiki/Cortex-A8" class="mw-redirect" title="Cortex-A8">Cortex-A8</a>, <a href="/wiki/Cortex-A9" class="mw-redirect" title="Cortex-A9">Cortex-A9</a>, <a href="/wiki/Cortex-A15" class="mw-redirect" title="Cortex-A15">Cortex-A15</a>, <a href="/wiki/Cortex-A17" class="mw-redirect" title="Cortex-A17">Cortex-A17</a>, <a href="/wiki/Cortex-A57" class="mw-redirect" title="Cortex-A57">Cortex-A57</a>, <a href="/wiki/Cortex-A72" class="mw-redirect" title="Cortex-A72">Cortex-A72</a>, and <a href="/wiki/Cortex-A73" class="mw-redirect" title="Cortex-A73">Cortex-A73</a> cores are affected only by the Spectre vulnerability.<a href="#cite_note-ARM_Security_Update-60">[60]</a> This contradicts some early statements made about the Meltdown vulnerability as being Intel-only.<a href="#cite_note-72">[72]</a> A large portion of the then-current mid-range <a href="/wiki/Android_(operating_system)" title="Android (operating system)">Android</a> handsets use the <a href="/wiki/Cortex-A53" class="mw-redirect" title="Cortex-A53">Cortex-A53</a> or <a href="/wiki/Cortex-A55" class="mw-redirect" title="Cortex-A55">Cortex-A55</a> in an <a href="/wiki/Octa-core" class="mw-redirect" title="Octa-core">octa-core</a> arrangement and are not affected by either the Meltdown or Spectre vulnerability as they do not perform out-of-order execution. This includes devices with the <a href="/wiki/Qualcomm_Snapdragon" title="Qualcomm Snapdragon">Qualcomm Snapdragon</a> 630, Snapdragon 626, Snapdragon 625, and all Snapdragon 4xx processors based on A53 or A55 cores.<a href="#cite_note-73">[73]</a> Also, no <a href="/wiki/Raspberry_Pi" title="Raspberry Pi">Raspberry Pi</a> computers are vulnerable to either Meltdown or Spectre, except the newly released Raspberry Pi 4, which uses the ARM Cortex-A72 CPU.<a href="#cite_note-74">[74]</a> IBM has also confirmed that its Power CPUs are affected by both CPU attacks.<a href="#cite_note-ibmpower-1">[1]</a> Red Hat has publicly announced that the exploits are also for <a href="/wiki/IBM_System_Z" class="mw-redirect" title="IBM System Z">IBM System Z</a>, <a href="/wiki/POWER8" title="POWER8">POWER8</a>, and <a href="/wiki/POWER9" title="POWER9">POWER9</a> systems.<a href="#cite_note-75">[75]</a> Oracle has stated that V9-based SPARC systems (T5, M5, M6, S7, M7, M8, M10, M12 processors) are not affected by Meltdown, though older SPARC processors that are no longer supported may be impacted.<a href="#cite_note-76">[76]</a> <div class="mw-heading mw-heading2"><h2 id="Mitigation">Mitigation</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=8" title="Edit section: Mitigation">edit</a>]</div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951" /><div role="note" class="hatnote navigation-not-searchable">Further information: <a href="/wiki/Kernel_page-table_isolation" title="Kernel page-table isolation">Kernel page-table isolation</a></div> Mitigation of the vulnerability requires changes to operating system kernel code, including increased isolation of kernel memory from user-mode processes.<a href="#cite_note-AT-20180105-4">[4]</a> <a href="/wiki/Linux_kernel" title="Linux kernel">Linux kernel</a> developers have referred to this measure as <a href="/wiki/Kernel_page-table_isolation" title="Kernel page-table isolation">kernel page-table isolation</a> (KPTI). KPTI patches have been developed for Linux kernel 4.15, and have been released as a <a href="/wiki/Backport" class="mw-redirect" title="Backport">backport</a> in kernels 4.14.11 and 4.9.75.<a href="#cite_note-77">[77]</a><a href="#cite_note-78">[78]</a><a href="#cite_note-79">[79]</a><a href="#cite_note-80">[80]</a> <a href="/wiki/Red_Hat" title="Red Hat">Red Hat</a> released kernel updates to their <a href="/wiki/Red_Hat_Enterprise_Linux" title="Red Hat Enterprise Linux">Red Hat Enterprise Linux</a> distributions version 6<a href="#cite_note-81">[81]</a> and version 7.<a href="#cite_note-82">[82]</a> <a href="/wiki/CentOS" title="CentOS">CentOS</a> also already released their kernel updates to CentOS 6<a href="#cite_note-83">[83]</a> and CentOS 7.<a href="#cite_note-84">[84]</a> Apple included mitigations in <a href="/wiki/MacOS" title="MacOS">macOS</a> 10.13.2, <a href="/wiki/IOS" title="IOS">iOS</a> 11.2, and <a href="/wiki/TvOS" title="TvOS">tvOS</a> 11.2. These were released a month before the vulnerabilities were made public.<a href="#cite_note-:0-85">[85]</a><a href="#cite_note-86">[86]</a><a href="#cite_note-87">[87]</a><a href="#cite_note-88">[88]</a> Apple has stated that <a href="/wiki/WatchOS" title="WatchOS">watchOS</a> and the <a href="/wiki/Apple_Watch" title="Apple Watch">Apple Watch</a> are not affected.<a href="#cite_note-89">[89]</a> Additional mitigations were included in a Safari update as well a supplemental update to macOS 10.13, and iOS 11.2.2.<a href="#cite_note-90">[90]</a><a href="#cite_note-91">[91]</a><a href="#cite_note-92">[92]</a><a href="#cite_note-93">[93]</a><a href="#cite_note-94">[94]</a> <a href="/wiki/Microsoft" title="Microsoft">Microsoft</a> released an emergency update to <a href="/wiki/Windows_10" title="Windows 10">Windows 10</a>, <a href="/wiki/Windows_8.1" title="Windows 8.1">8.1</a>, and <a href="/wiki/Windows_7" title="Windows 7">7 SP1</a> to address the vulnerability on 3 January 2018,<a href="#cite_note-95">[95]</a><a href="#cite_note-96">[96]</a><a href="#cite_note-97">[97]</a> as well as <a href="/wiki/Windows_Server" title="Windows Server">Windows Server</a> (including <a href="/wiki/Windows_Server_2008_R2" title="Windows Server 2008 R2">Server 2008 R2</a>, <a href="/wiki/Windows_Server_2012_R2" title="Windows Server 2012 R2">Server 2012 R2</a>, and <a href="/wiki/Windows_Server_2016" title="Windows Server 2016">Server 2016</a>) and <a href="/wiki/Windows_Embedded_Industry" title="Windows Embedded Industry">Windows Embedded Industry</a>.<a href="#cite_note-98">[98]</a> These patches are incompatible with third-party antivirus software that use unsupported kernel calls; systems running incompatible antivirus software will not receive this or any future Windows security updates until it is patched, and the software adds a special <a href="/wiki/Registry_key" class="mw-redirect" title="Registry key">registry key</a> affirming its compatibility.<a href="#cite_note-msamdissue-zdnet-99">[99]</a><a href="#cite_note-100">[100]</a><a href="#cite_note-101">[101]</a> The update was found to have caused issues on systems running certain AMD CPUs, with some users reporting that their Windows installations did not boot at all after installation. On 9 January 2018, Microsoft paused the distribution of the update to systems with affected CPUs while it investigated and addressed this bug.<a href="#cite_note-msamdissue-zdnet-99">[99]</a> It was reported that implementation of KPTI may lead to a reduction in CPU performance, with some researchers claiming up to 30% loss in performance, depending on usage, though Intel considered this to be an exaggeration.<a href="#cite_note-bbcflaw-19">[19]</a> It was reported that Intel processor generations that support <a href="/wiki/Process-context_identifier" class="mw-redirect" title="Process-context identifier">process-context identifiers</a> (PCID), a feature introduced with <a href="/wiki/Westmere_(microarchitecture)" title="Westmere (microarchitecture)">Westmere</a><a href="#cite_note-102">[102]</a> and available on all chips from the <a href="/wiki/Haswell_(microarchitecture)" title="Haswell (microarchitecture)">Haswell</a> architecture onward, were not as susceptible to performance losses under KPTI as older generations that lack it.<a href="#cite_note-103">[103]</a><a href="#cite_note-104">[104]</a> This is because the selective translation lookaside buffer (TLB) flushing enabled by PCID (also called <a href="/wiki/Address_space_number" class="mw-redirect" title="Address space number">address space number</a> or ASN under the Alpha architecture) enables the shared TLB behavior crucial to the exploit to be isolated across processes, without constantly flushing the entire cache – the primary reason for the cost of mitigation. A statement by Intel said that "any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time".<a href="#cite_note-TV-20180104-21">[21]</a><a href="#cite_note-NYT-20180103-20">[20]</a> <a href="/wiki/Phoronix" class="mw-redirect" title="Phoronix">Phoronix</a> benchmarked several popular PC games on a Linux system with Intel's <a href="/wiki/Coffee_Lake" title="Coffee Lake">Coffee Lake</a> Core i7-8700K CPU and KPTI patches installed, and found that any performance impact was small to non-existent.<a href="#cite_note-auto-62">[62]</a> In other tests, including synthetic I/O benchmarks and databases such as <a href="/wiki/PostgreSQL" title="PostgreSQL">PostgreSQL</a> and <a href="/wiki/Redis" title="Redis">Redis</a>, an impact in performance was found, accounting even to tens of percent for some workloads.<a href="#cite_note-105">[105]</a> More recently, related tests, involving AMD's <a href="/wiki/AMD_FX" title="AMD FX">FX</a> and Intel's <a href="/wiki/Sandy_Bridge" title="Sandy Bridge">Sandybridge</a> and <a href="/wiki/Ivy_Bridge_(microarchitecture)" title="Ivy Bridge (microarchitecture)">Ivybridge</a> CPUs, have been reported.<a href="#cite_note-PH-20190524-106">[106]</a> Several procedures to help protect home computers and related devices from the Meltdown and Spectre security vulnerabilities have been published.<a href="#cite_note-NYT-20180104-15">[15]</a><a href="#cite_note-FM-20180105-16">[16]</a><a href="#cite_note-PCW-20180104-17">[17]</a><a href="#cite_note-CNET-20180104-18">[18]</a> Meltdown patches may produce performance loss.<a href="#cite_note-bbcflaw-19">[19]</a><a href="#cite_note-NYT-20180103-20">[20]</a><a href="#cite_note-TV-20180104-21">[21]</a> On 18 January 2018, unwanted reboots, even for newer Intel chips, due to Meltdown and Spectre patches, were reported.<a href="#cite_note-ZDN-20180118-23">[23]</a> According to <a href="/wiki/Dell" title="Dell">Dell</a>, "No 'real-world' exploits of these vulnerabilities [ie, Meltdown and Spectre] have been reported to date [26 January 2018], though researchers have produced proof-of-concepts."<a href="#cite_note-DELL-20180126a-24">[24]</a><a href="#cite_note-DELL-20180126b-25">[25]</a> Dell further recommended "promptly adopting software updates, avoiding unrecognized hyperlinks and websites, not downloading files or applications from unknown sources ... following secure password protocols ... [using] security software to help protect against malware (advanced threat prevention software or anti-virus)."<a href="#cite_note-DELL-20180126a-24">[24]</a><a href="#cite_note-DELL-20180126b-25">[25]</a> On 25 January 2018, the current status and possible future considerations in solving the Meltdown and Spectre vulnerabilities were presented.<a href="#cite_note-PC-20180125-107">[107]</a> In March 2018, Intel announced that it had designed hardware fixes for future processors for Meltdown and Spectre-V2 only, but not Spectre-V1. The vulnerabilities were mitigated by a new partitioning system that improves process and privilege-level separation. The company also announced it had developed workarounds in <a href="/wiki/Intel_microcode" title="Intel microcode">microcode</a> for processors dating back to 2013, and that it had plans to develop them for most processors dating back to 2007 including the <a href="/wiki/Penryn_(microprocessor)" title="Penryn (microprocessor)">Core 2 Duo</a>;<a href="#cite_note-AT-20180315-28">[28]</a><a href="#cite_note-TC-20180315-29">[29]</a> however, a month later in April 2018, it announced it was backing off that plan for a number of processor families and that no processor earlier than 2008 would have a patch available.<a href="#cite_note-108">[108]</a> On 8 October 2018, Intel was reported to have added hardware and firmware mitigations regarding Spectre and Meltdown vulnerabilities to its latest processors.<a href="#cite_note-AT-20181008-30">[30]</a> <table class="wikitable"> <caption>Summary of mitigations on Microsoft Windows<a href="#cite_note-109">[109]</a> </caption> <tbody><tr> <th>Vulnerability</th> <th>CVE</th> <th>Exploit name</th> <th>Public vulnerability name</th> <th>Windows changes</th> <th>Firmware changes </th></tr> <tr> <td>(Spectre)</td> <td>2017-5753</td> <td>Variant 1</td> <td>Bounds Check Bypass (BCB)</td> <td><style data-mw-deduplicate="TemplateStyles:r1126788409">.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}</style><div class="plainlist"><ul><li>Recompiling with a new compiler</li><li>Hardened browser to prevent exploit from JavaScript</li></ul></div></td> <td>No </td></tr> <tr> <td>(Spectre)</td> <td>2017-5715</td> <td>Variant 2</td> <td>Branch Target Injection (BTI)</td> <td>New CPU instructions eliminating branch speculation</td> <td>Yes </td></tr> <tr> <td>Meltdown</td> <td>2017-5754</td> <td>Variant 3</td> <td>Rogue Data Cache Load (RDCL)</td> <td><a href="/wiki/Kernel_page-table_isolation" title="Kernel page-table isolation">Isolate kernel and user mode page tables</a></td> <td>No </td></tr></tbody></table> <div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=9" title="Edit section: See also">edit</a>]</div> <ul><li><a href="/wiki/Intel_Management_Engine" title="Intel Management Engine">Intel Management Engine</a> – an Intel subsystem which was discovered to have a major security vulnerability in 2017</li> <li><a href="/wiki/Pentium_F00F_bug" title="Pentium F00F bug">Pentium F00F bug</a></li> <li><a href="/wiki/Pentium_FDIV_bug" title="Pentium FDIV bug">Pentium FDIV bug</a></li> <li><a href="/wiki/Row_hammer" title="Row hammer">Row hammer</a> – an unintended side effect in dynamic random-access memory causing memory cells to interact electrically</li> <li><a href="/wiki/Spoiler_(security_vulnerability)" title="Spoiler (security vulnerability)">Spoiler</a> − a Spectre-like, though unrelated, vulnerability affecting only Intel microprocessors, disclosed in 2019.</li></ul> <div class="mw-heading mw-heading2"><h2 id="References">References</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=10" title="Edit section: References">edit</a>]</div> <style data-mw-deduplicate="TemplateStyles:r1239543626">.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}</style><div class="reflist"> <div class="mw-references-wrap mw-references-columns"><ol class="references"> <li id="cite_note-ibmpower-1">^ <a href="#cite_ref-ibmpower_1-0">a</a> <a href="#cite_ref-ibmpower_1-1">b</a> <a href="#cite_ref-ibmpower_1-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.ibm.com/blogs/psirt/potential-impact-processors-power-family/">"Potential Impact on Processors in the POWER Family – IBM PSIRT Blog"</a>. IBM.com. 2018-01-25. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180403044519/https://www.ibm.com/blogs/psirt/potential-impact-processors-power-family/">Archived</a> from the original on 2018-04-03. Retrieved 2018-01-30.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=IBM.com&rft.atitle=Potential+Impact+on+Processors+in+the+POWER+Family+%E2%80%93+IBM+PSIRT+Blog&rft.date=2018-01-25&rft_id=https%3A%2F%2Fwww.ibm.com%2Fblogs%2Fpsirt%2Fpotential-impact-processors-power-family%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-2"><a href="#cite_ref-2">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208394">"About speculative execution vulnerabilities in ARM-based and Intel CPUs"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210327083711/https://support.apple.com/en-us/HT208394">Archived</a> from the original on 2021-03-27. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Apple+Support&rft.atitle=About+speculative+execution+vulnerabilities+in+ARM-based+and+Intel+CPUs&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208394&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-auto1-3">^ <a href="#cite_ref-auto1_3-0">a</a> <a href="#cite_ref-auto1_3-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFArm_Ltd." class="citation web cs1"><a href="/wiki/Arm_Ltd." class="mw-redirect" title="Arm Ltd.">Arm Ltd.</a> <a rel="nofollow" class="external text" href="https://developer.arm.com/support/security-update">"Arm Processor Security Update"</a>. ARM Developer. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180404110048/https://developer.arm.com/support/security-update">Archived</a> from the original on 2018-04-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=ARM+Developer&rft.atitle=Arm+Processor+Security+Update&rft.au=Arm+Ltd.&rft_id=https%3A%2F%2Fdeveloper.arm.com%2Fsupport%2Fsecurity-update&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-AT-20180105-4">^ <a href="#cite_ref-AT-20180105_4-0">a</a> <a href="#cite_ref-AT-20180105_4-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFBright2018" class="citation web cs1">Bright, Peter (2018-01-05). <a rel="nofollow" class="external text" href="https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/">"Meltdown and Spectre: Here's what Intel, Apple, Microsoft, others are doing about it"</a>. <a href="/wiki/Ars_Technica" title="Ars Technica">Ars Technica</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180527032912/https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/">Archived</a> from the original on 2018-05-27. Retrieved 2018-01-06.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Ars+Technica&rft.atitle=Meltdown+and+Spectre%3A+Here%27s+what+Intel%2C+Apple%2C+Microsoft%2C+others+are+doing+about+it&rft.date=2018-01-05&rft.aulast=Bright&rft.aufirst=Peter&rft_id=https%3A%2F%2Farstechnica.com%2Fgadgets%2F2018%2F01%2Fmeltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-:1-5">^ <a href="#cite_ref-:1_5-0">a</a> <a href="#cite_ref-:1_5-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.macrumors.com/2018/01/04/apple-meltdown-spectre-vulnerability-fixes/">"Apple Confirms 'Meltdown' and 'Spectre' Vulnerabilities Impact All Macs and iOS Devices, Some Fixes Already Released"</a>. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201205224604/https://www.macrumors.com/2018/01/04/apple-meltdown-spectre-vulnerability-fixes/">Archived</a> from the original on 2020-12-05. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Apple+Confirms+%27Meltdown%27+and+%27Spectre%27+Vulnerabilities+Impact+All+Macs+and+iOS+Devices%2C+Some+Fixes+Already+Released&rft.date=2018-01-04&rft_id=https%3A%2F%2Fwww.macrumors.com%2F2018%2F01%2F04%2Fapple-meltdown-spectre-vulnerability-fixes%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-6"><a href="#cite_ref-6">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFVaughan-Nichols2018" class="citation news cs1">Vaughan-Nichols, Steven J. (2018-01-11). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/major-linux-distros-have-meltdown-patches-but-thats-only-part-of-the-fix/">"Major Linux distros have Meltdown patches, but that's only part of the fix"</a>. <a href="/wiki/ZDNet" class="mw-redirect" title="ZDNet">ZDNet</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201109011759/https://www.zdnet.com/article/major-linux-distros-have-meltdown-patches-but-thats-only-part-of-the-fix/">Archived</a> from the original on 2020-11-09. Retrieved 2018-01-16.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=ZDNet&rft.atitle=Major+Linux+distros+have+Meltdown+patches%2C+but+that%27s+only+part+of+the+fix&rft.date=2018-01-11&rft.aulast=Vaughan-Nichols&rft.aufirst=Steven+J.&rft_id=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fmajor-linux-distros-have-meltdown-patches-but-thats-only-part-of-the-fix%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-7"><a href="#cite_ref-7">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://security-tracker.debian.org/tracker/CVE-2017-5754">"CVE-2017-5754"</a>. Security-Tracker.Debian.org. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210412050627/https://security-tracker.debian.org/tracker/CVE-2017-5754">Archived</a> from the original on 2021-04-12. Retrieved 2018-01-16.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Security-Tracker.Debian.org&rft.atitle=CVE-2017-5754&rft_id=https%3A%2F%2Fsecurity-tracker.debian.org%2Ftracker%2FCVE-2017-5754&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-8"><a href="#cite_ref-8">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://winbuzzer.com/2018/01/04/cert-warns-way-fix-intel-kernel-security-flaw-replace-cpu-xcxwbn">"CERT: "Meltdown and Spectre" CPU Security Flaw Can Only Be Fixed by Hardware Replacement – WinBuzzer"</a>. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210508103537/https://winbuzzer.com/2018/01/04/cert-warns-way-fix-intel-kernel-security-flaw-replace-cpu-xcxwbn/">Archived</a> from the original on 2021-05-08. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=CERT%3A+%22Meltdown+and+Spectre%22+CPU+Security+Flaw+Can+Only+Be+Fixed+by+Hardware+Replacement+%E2%80%93+WinBuzzer&rft.date=2018-01-04&rft_id=https%3A%2F%2Fwinbuzzer.com%2F2018%2F01%2F04%2Fcert-warns-way-fix-intel-kernel-security-flaw-replace-cpu-xcxwbn&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-register-9">^ <a href="#cite_ref-register_9-0">a</a> <a href="#cite_ref-register_9-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/">"Kernel-memory-leaking Intel processor design flaw forces Linux, Windows redesign"</a>. The Register. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180407091509/http://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/">Archived</a> from the original on 2018-04-07. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=The+Register&rft.atitle=Kernel-memory-leaking+Intel+processor+design+flaw+forces+Linux%2C+Windows+redesign&rft_id=https%3A%2F%2Fwww.theregister.co.uk%2F2018%2F01%2F02%2Fintel_cpu_design_flaw%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-10"><a href="#cite_ref-10">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://newsroom.intel.com/news-releases/industry-testing-shows-recently-released-security-updates-not-impacting-performance-real-world-deployments/">"Industry Testing Shows Recently Released Security Updates Not Impacting Performance in Real-World Deployments"</a>. Intel newsroom. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20211006122040/https://newsroom.intel.com/news-releases/industry-testing-shows-recently-released-security-updates-not-impacting-performance-real-world-deployments/">Archived</a> from the original on 2021-10-06. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Intel+newsroom&rft.atitle=Industry+Testing+Shows+Recently+Released+Security+Updates+Not+Impacting+Performance+in+Real-World+Deployments&rft.date=2018-01-04&rft_id=https%3A%2F%2Fnewsroom.intel.com%2Fnews-releases%2Findustry-testing-shows-recently-released-security-updates-not-impacting-performance-real-world-deployments%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-11"><a href="#cite_ref-11">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFSchneier" class="citation web cs1"><a href="/wiki/Bruce_Schneier" title="Bruce Schneier">Schneier, Bruce</a>. <a rel="nofollow" class="external text" href="https://www.schneier.com/blog/archives/2018/01/spectre_and_mel_1.html">"Spectre and Meltdown Attacks Against Microprocessors – Schneier on Security"</a>. Schneier.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210412075738/https://www.schneier.com/blog/archives/2018/01/spectre_and_mel_1.html">Archived</a> from the original on 2021-04-12. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Schneier.com&rft.atitle=Spectre+and+Meltdown+Attacks+Against+Microprocessors+%E2%80%93+Schneier+on+Security&rft.aulast=Schneier&rft.aufirst=Bruce&rft_id=https%3A%2F%2Fwww.schneier.com%2Fblog%2Farchives%2F2018%2F01%2Fspectre_and_mel_1.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-12"><a href="#cite_ref-12">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cylance.com/en_us/blog/this-week-in-security-internet-meltdown-over-spectre-of-cpu-bug.html">"This Week in Security: Internet Meltdown Over Spectre of CPU Bug"</a>. Cylance.com. 2018-01-05. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180109063929/https://www.cylance.com/en_us/blog/this-week-in-security-internet-meltdown-over-spectre-of-cpu-bug.html">Archived</a> from the original on 2018-01-09. Retrieved 2018-01-30.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Cylance.com&rft.atitle=This+Week+in+Security%3A+Internet+Meltdown+Over+Spectre+of+CPU+Bug&rft.date=2018-01-05&rft_id=https%3A%2F%2Fwww.cylance.com%2Fen_us%2Fblog%2Fthis-week-in-security-internet-meltdown-over-spectre-of-cpu-bug.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-13"><a href="#cite_ref-13">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.rudebaguette.com/2018/01/meltdown-spectre-heres-what-you-should-know/">"Meltdown, Spectre: here's what you should know"</a>. Rudebaguette.com. 2018-01-08. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180705232842/http://www.rudebaguette.com/2018/01/08/meltdown-spectre-heres-what-you-should-know/">Archived</a> from the original on 2018-07-05. Retrieved 2018-01-30.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Rudebaguette.com&rft.atitle=Meltdown%2C+Spectre%3A+here%27s+what+you+should+know&rft.date=2018-01-08&rft_id=https%3A%2F%2Fwww.rudebaguette.com%2F2018%2F01%2Fmeltdown-spectre-heres-what-you-should-know%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-14"><a href="#cite_ref-14">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFKingKahnWebbTurner2018" class="citation journal cs1">King, Ian; Kahn, Jeremy; Webb, Alex; Turner, Giles (2018-01-08). <a rel="nofollow" class="external text" href="https://www.bloomberg.com/news/articles/2018-01-08/-it-can-t-be-true-inside-the-semiconductor-industry-s-meltdown">"'It Can't Be True.' Inside the Semiconductor Industry's Meltdown"</a>. <a href="/wiki/Bloomberg_Technology" title="Bloomberg Technology">Bloomberg Technology</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180110032657/https://www.bloomberg.com/news/articles/2018-01-08/-it-can-t-be-true-inside-the-semiconductor-industry-s-meltdown">Archived</a> from the original on 2018-01-10. Retrieved 2018-01-10.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Bloomberg+Technology&rft.atitle=%27It+Can%27t+Be+True.%27+Inside+the+Semiconductor+Industry%27s+Meltdown&rft.date=2018-01-08&rft.aulast=King&rft.aufirst=Ian&rft.au=Kahn%2C+Jeremy&rft.au=Webb%2C+Alex&rft.au=Turner%2C+Giles&rft_id=https%3A%2F%2Fwww.bloomberg.com%2Fnews%2Farticles%2F2018-01-08%2F-it-can-t-be-true-inside-the-semiconductor-industry-s-meltdown&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-NYT-20180104-15">^ <a href="#cite_ref-NYT-20180104_15-0">a</a> <a href="#cite_ref-NYT-20180104_15-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFMetzChen2018" class="citation news cs1">Metz, Cade; Chen, Brian X. (2018-01-04). <a rel="nofollow" class="external text" href="https://www.nytimes.com/2018/01/04/technology/meltdown-spectre-questions.html">"What You Need to Do Because of Flaws in Computer Chips"</a>. <a href="/wiki/The_New_York_Times" title="The New York Times">The New York Times</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180106155009/https://www.nytimes.com/2018/01/04/technology/meltdown-spectre-questions.html">Archived</a> from the original on 2018-01-06. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=The+New+York+Times&rft.atitle=What+You+Need+to+Do+Because+of+Flaws+in+Computer+Chips&rft.date=2018-01-04&rft.aulast=Metz&rft.aufirst=Cade&rft.au=Chen%2C+Brian+X.&rft_id=https%3A%2F%2Fwww.nytimes.com%2F2018%2F01%2F04%2Ftechnology%2Fmeltdown-spectre-questions.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-FM-20180105-16">^ <a href="#cite_ref-FM-20180105_16-0">a</a> <a href="#cite_ref-FM-20180105_16-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFPressman2018" class="citation web cs1">Pressman, Aaron (2018-01-05). <a rel="nofollow" class="external text" href="http://fortune.com/2018/01/05/spectre-safari-chrome-firefox-internet-explorer/">"Why Your Web Browser May Be Most Vulnerable to Spectre and What to Do About It"</a>. <a href="/wiki/Fortune_(magazine)" title="Fortune (magazine)">Fortune</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180110161156/http://fortune.com/2018/01/05/spectre-safari-chrome-firefox-internet-explorer/">Archived</a> from the original on 2018-01-10. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Fortune&rft.atitle=Why+Your+Web+Browser+May+Be+Most+Vulnerable+to+Spectre+and+What+to+Do+About+It&rft.date=2018-01-05&rft.aulast=Pressman&rft.aufirst=Aaron&rft_id=http%3A%2F%2Ffortune.com%2F2018%2F01%2F05%2Fspectre-safari-chrome-firefox-internet-explorer%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-PCW-20180104-17">^ <a href="#cite_ref-PCW-20180104_17-0">a</a> <a href="#cite_ref-PCW-20180104_17-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFChacos2018" class="citation web cs1">Chacos, Brad (2018-01-04). <a rel="nofollow" class="external text" href="https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html">"How to protect your PC from the major Meltdown and Spectre CPU flaws"</a>. <a href="/wiki/PC_World" title="PC World">PC World</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104231745/https://www.pcworld.com/article/3245810/security/how-to-protect-your-pc-meltdown-spectre-cpu-flaws.html">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=PC+World&rft.atitle=How+to+protect+your+PC+from+the+major+Meltdown+and+Spectre+CPU+flaws&rft.date=2018-01-04&rft.aulast=Chacos&rft.aufirst=Brad&rft_id=https%3A%2F%2Fwww.pcworld.com%2Farticle%2F3245810%2Fsecurity%2Fhow-to-protect-your-pc-meltdown-spectre-cpu-flaws.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-CNET-20180104-18">^ <a href="#cite_ref-CNET-20180104_18-0">a</a> <a href="#cite_ref-CNET-20180104_18-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFElliot2018" class="citation web cs1">Elliot, Matt (2018-01-04). <a rel="nofollow" class="external text" href="https://www.cnet.com/how-to/how-to-protect-your-pc-against-the-intel-chip-flaw/">"Security – How to protect your PC against the Intel chip flaw – Here are the steps to take to keep your Windows laptop or PC safe from Meltdown and Spectre"</a>. <a href="/wiki/CNET" title="CNET">CNET</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104225045/https://www.cnet.com/how-to/how-to-protect-your-pc-against-the-intel-chip-flaw/">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=CNET&rft.atitle=Security+%E2%80%93+How+to+protect+your+PC+against+the+Intel+chip+flaw+%E2%80%93+Here+are+the+steps+to+take+to+keep+your+Windows+laptop+or+PC+safe+from+Meltdown+and+Spectre.&rft.date=2018-01-04&rft.aulast=Elliot&rft.aufirst=Matt&rft_id=https%3A%2F%2Fwww.cnet.com%2Fhow-to%2Fhow-to-protect-your-pc-against-the-intel-chip-flaw%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-bbcflaw-19">^ <a href="#cite_ref-bbcflaw_19-0">a</a> <a href="#cite_ref-bbcflaw_19-1">b</a> <a href="#cite_ref-bbcflaw_19-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.bbc.com/news/technology-42562303">"Computer chip scare: What you need to know"</a>. <a href="/wiki/BBC_News" title="BBC News">BBC News</a>. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201011235525/https://www.bbc.com/news/technology-42562303">Archived</a> from the original on 2020-10-11. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=BBC+News&rft.atitle=Computer+chip+scare%3A+What+you+need+to+know&rft.date=2018-01-04&rft_id=https%3A%2F%2Fwww.bbc.com%2Fnews%2Ftechnology-42562303&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-NYT-20180103-20">^ <a href="#cite_ref-NYT-20180103_20-0">a</a> <a href="#cite_ref-NYT-20180103_20-1">b</a> <a href="#cite_ref-NYT-20180103_20-2">c</a> <a href="#cite_ref-NYT-20180103_20-3">d</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFMetzPerlroth2018" class="citation news cs1">Metz, Cade; Perlroth, Nicole (2018-01-03). <a rel="nofollow" class="external text" href="https://www.nytimes.com/2018/01/03/business/computer-flaws.html">"Researchers Discover Two Major Flaws in the World's Computers"</a>. The New York Times. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0362-4331">0362-4331</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103224048/https://www.nytimes.com/2018/01/03/business/computer-flaws.html">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=The+New+York+Times&rft.atitle=Researchers+Discover+Two+Major+Flaws+in+the+World%27s+Computers&rft.date=2018-01-03&rft.issn=0362-4331&rft.aulast=Metz&rft.aufirst=Cade&rft.au=Perlroth%2C+Nicole&rft_id=https%3A%2F%2Fwww.nytimes.com%2F2018%2F01%2F03%2Fbusiness%2Fcomputer-flaws.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-TV-20180104-21">^ <a href="#cite_ref-TV-20180104_21-0">a</a> <a href="#cite_ref-TV-20180104_21-1">b</a> <a href="#cite_ref-TV-20180104_21-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.theverge.com/2018/1/3/16846540/intel-processor-security-flaw-bug-response">"Intel says processor bug isn't unique to its chips and performance issues are 'workload-dependent'"</a>. The Verge. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103223052/https://www.theverge.com/2018/1/3/16846540/intel-processor-security-flaw-bug-response">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=The+Verge&rft.atitle=Intel+says+processor+bug+isn%27t+unique+to+its+chips+and+performance+issues+are+%27workload-dependent%27&rft_id=https%3A%2F%2Fwww.theverge.com%2F2018%2F1%2F3%2F16846540%2Fintel-processor-security-flaw-bug-response&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-PCW-20180109-22"><a href="#cite_ref-PCW-20180109_22-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFHachman2018" class="citation web cs1">Hachman, Mark (2018-01-09). <a rel="nofollow" class="external text" href="https://www.pcworld.com/article/3245742/components-processors/microsoft-tests-show-spectre-patches-drag-down-performance-on-older-pcs.html">"Microsoft tests show Spectre patches drag down performance on older PCs"</a>. <a href="/wiki/PC_World" title="PC World">PC World</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180209120423/https://www.pcworld.com/article/3245742/components-processors/microsoft-tests-show-spectre-patches-drag-down-performance-on-older-pcs.html">Archived</a> from the original on 2018-02-09. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=PC+World&rft.atitle=Microsoft+tests+show+Spectre+patches+drag+down+performance+on+older+PCs&rft.date=2018-01-09&rft.aulast=Hachman&rft.aufirst=Mark&rft_id=https%3A%2F%2Fwww.pcworld.com%2Farticle%2F3245742%2Fcomponents-processors%2Fmicrosoft-tests-show-spectre-patches-drag-down-performance-on-older-pcs.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-ZDN-20180118-23">^ <a href="#cite_ref-ZDN-20180118_23-0">a</a> <a href="#cite_ref-ZDN-20180118_23-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFTung2018" class="citation web cs1">Tung, Liam (2018-01-18). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/meltdown-spectre-intel-says-newer-chips-also-hit-by-unwanted-reboots-after-patch/">"Meltdown-Spectre: Intel says newer chips also hit by unwanted reboots after patch – Intel's firmware fix for Spectre is also causing higher reboots on Kaby Lake and Skylake CPUs"</a>. <a href="/wiki/ZDNet" class="mw-redirect" title="ZDNet">ZDNet</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180120213941/https://www.zdnet.com/article/meltdown-spectre-intel-says-newer-chips-also-hit-by-unwanted-reboots-after-patch/">Archived</a> from the original on 2018-01-20. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=ZDNet&rft.atitle=Meltdown-Spectre%3A+Intel+says+newer+chips+also+hit+by+unwanted+reboots+after+patch+%E2%80%93+Intel%27s+firmware+fix+for+Spectre+is+also+causing+higher+reboots+on+Kaby+Lake+and+Skylake+CPUs&rft.date=2018-01-18&rft.aulast=Tung&rft.aufirst=Liam&rft_id=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fmeltdown-spectre-intel-says-newer-chips-also-hit-by-unwanted-reboots-after-patch%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-DELL-20180126a-24">^ <a href="#cite_ref-DELL-20180126a_24-0">a</a> <a href="#cite_ref-DELL-20180126a_24-1">b</a> <a href="#cite_ref-DELL-20180126a_24-2">c</a> <a href="#cite_ref-DELL-20180126a_24-3">d</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFStaff2018" class="citation web cs1">Staff (2018-01-26). <a rel="nofollow" class="external text" href="https://www.dell.com/support/kbdoc/en-us/000180621/microprocessor-side-channel-vulnerabilities-cve-2017-5715-cve-2017-5753-cve-2017-5754-impact-on-dell-products">"Microprocessor Side-Channel Vulnerabilities (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754): Impact on Dell products"</a>. <a href="/wiki/Dell" title="Dell">Dell</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180127083842/http://www.dell.com/support/article/us/en/19/sln308587/microprocessor-side-channel-vulnerabilities-cve-2017-5715-cve-2017-5753-cve-2017-5754-impact-on-dell-products?lang=en">Archived</a> from the original on 2018-01-27. Retrieved 2018-01-26.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Dell&rft.atitle=Microprocessor+Side-Channel+Vulnerabilities+%28CVE-2017-5715%2C+CVE-2017-5753%2C+CVE-2017-5754%29%3A+Impact+on+Dell+products&rft.date=2018-01-26&rft.au=Staff&rft_id=https%3A%2F%2Fwww.dell.com%2Fsupport%2Fkbdoc%2Fen-us%2F000180621%2Fmicroprocessor-side-channel-vulnerabilities-cve-2017-5715-cve-2017-5753-cve-2017-5754-impact-on-dell-products&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-DELL-20180126b-25">^ <a href="#cite_ref-DELL-20180126b_25-0">a</a> <a href="#cite_ref-DELL-20180126b_25-1">b</a> <a href="#cite_ref-DELL-20180126b_25-2">c</a> <a href="#cite_ref-DELL-20180126b_25-3">d</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFStaff2018" class="citation web cs1">Staff (2018-01-26). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180305000921/http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre">"Meltdown and Spectre Vulnerabilities"</a>. <a href="/wiki/Dell" title="Dell">Dell</a>. Archived from <a rel="nofollow" class="external text" href="http://www.dell.com/support/contents/us/en/19/article/product-support/self-support-knowledgebase/software-and-downloads/support-for-meltdown-and-spectre">the original</a> on 2018-03-05. Retrieved 2018-01-26.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Dell&rft.atitle=Meltdown+and+Spectre+Vulnerabilities&rft.date=2018-01-26&rft.au=Staff&rft_id=http%3A%2F%2Fwww.dell.com%2Fsupport%2Fcontents%2Fus%2Fen%2F19%2Farticle%2Fproduct-support%2Fself-support-knowledgebase%2Fsoftware-and-downloads%2Fsupport-for-meltdown-and-spectre&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-TVRG-20180315-26"><a href="#cite_ref-TVRG-20180315_26-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFWarren2018" class="citation news cs1">Warren, Tom (2018-03-15). <a rel="nofollow" class="external text" href="https://www.theverge.com/2018/3/15/17123610/intel-new-processors-protection-spectre-vulnerability">"Intel processors are being redesigned to protect against Spectre – New hardware coming later this year"</a>. <a href="/wiki/The_Verge" title="The Verge">The Verge</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180421124711/https://www.theverge.com/2018/3/15/17123610/intel-new-processors-protection-spectre-vulnerability">Archived</a> from the original on 2018-04-21. Retrieved 2018-03-20.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=The+Verge&rft.atitle=Intel+processors+are+being+redesigned+to+protect+against+Spectre+%E2%80%93+New+hardware+coming+later+this+year&rft.date=2018-03-15&rft.aulast=Warren&rft.aufirst=Tom&rft_id=https%3A%2F%2Fwww.theverge.com%2F2018%2F3%2F15%2F17123610%2Fintel-new-processors-protection-spectre-vulnerability&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-CNET-20180315-27"><a href="#cite_ref-CNET-20180315_27-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFShankland2018" class="citation news cs1">Shankland, Stephen (2018-03-15). <a rel="nofollow" class="external text" href="https://www.cnet.com/news/intel-blocks-spectre-attacks-with-new-server-chips-this-year/">"Intel will block Spectre attacks with new chips this year – Cascade Lake processors for servers, coming this year, will fight back against a new class of vulnerabilities, says CEO Brian Krzanich"</a>. <a href="/wiki/CNET" title="CNET">CNET</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180423050703/https://www.cnet.com/news/intel-blocks-spectre-attacks-with-new-server-chips-this-year/">Archived</a> from the original on 2018-04-23. Retrieved 2018-03-20.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=CNET&rft.atitle=Intel+will+block+Spectre+attacks+with+new+chips+this+year+%E2%80%93+Cascade+Lake+processors+for+servers%2C+coming+this+year%2C+will+fight+back+against+a+new+class+of+vulnerabilities%2C+says+CEO+Brian+Krzanich.&rft.date=2018-03-15&rft.aulast=Shankland&rft.aufirst=Stephen&rft_id=https%3A%2F%2Fwww.cnet.com%2Fnews%2Fintel-blocks-spectre-attacks-with-new-server-chips-this-year%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-AT-20180315-28">^ <a href="#cite_ref-AT-20180315_28-0">a</a> <a href="#cite_ref-AT-20180315_28-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFSmith2018" class="citation web cs1">Smith, Ryan (2018-03-15). <a rel="nofollow" class="external text" href="https://www.anandtech.com/show/12533/intel-spectre-meltdown">"Intel Publishes Spectre & Meltdown Hardware Plans: Fixed Gear Later This Year"</a>. <a href="/wiki/AnandTech" title="AnandTech">AnandTech</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180504075207/https://www.anandtech.com/show/12533/intel-spectre-meltdown">Archived</a> from the original on 2018-05-04. Retrieved 2018-03-20.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=AnandTech&rft.atitle=Intel+Publishes+Spectre+%26+Meltdown+Hardware+Plans%3A+Fixed+Gear+Later+This+Year&rft.date=2018-03-15&rft.aulast=Smith&rft.aufirst=Ryan&rft_id=https%3A%2F%2Fwww.anandtech.com%2Fshow%2F12533%2Fintel-spectre-meltdown&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-TC-20180315-29">^ <a href="#cite_ref-TC-20180315_29-0">a</a> <a href="#cite_ref-TC-20180315_29-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFColdewey2018" class="citation web cs1">Coldewey, Devin (2018-03-15). <a rel="nofollow" class="external text" href="https://techcrunch.com/2018/03/15/intel-announces-hardware-fixes-for-spectre-and-meltdown-on-upcoming-chips/">"Intel announces hardware fixes for Spectre and Meltdown on upcoming chips"</a>. <a href="/wiki/TechCrunch" title="TechCrunch">TechCrunch</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180412164033/https://techcrunch.com/2018/03/15/intel-announces-hardware-fixes-for-spectre-and-meltdown-on-upcoming-chips/">Archived</a> from the original on 2018-04-12. Retrieved 2018-03-28.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=TechCrunch&rft.atitle=Intel+announces+hardware+fixes+for+Spectre+and+Meltdown+on+upcoming+chips&rft.date=2018-03-15&rft.aulast=Coldewey&rft.aufirst=Devin&rft_id=https%3A%2F%2Ftechcrunch.com%2F2018%2F03%2F15%2Fintel-announces-hardware-fixes-for-spectre-and-meltdown-on-upcoming-chips%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-AT-20181008-30">^ <a href="#cite_ref-AT-20181008_30-0">a</a> <a href="#cite_ref-AT-20181008_30-1">b</a> <a href="#cite_ref-AT-20181008_30-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFShilov2018" class="citation web cs1">Shilov, Anton (2018-10-08). <a rel="nofollow" class="external text" href="https://www.anandtech.com/show/13450/intels-new-core-and-xeon-w-processors-fixes-for-spectre-meltdown">"Intel's New Core and Xeon W-3175X Processors: Spectre and Meltdown Security Update"</a>. <a href="/wiki/AnandTech" title="AnandTech">AnandTech</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20181009051844/https://www.anandtech.com/show/13450/intels-new-core-and-xeon-w-processors-fixes-for-spectre-meltdown">Archived</a> from the original on 2018-10-09. Retrieved 2018-10-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=AnandTech&rft.atitle=Intel%27s+New+Core+and+Xeon+W-3175X+Processors%3A+Spectre+and+Meltdown+Security+Update&rft.date=2018-10-08&rft.aulast=Shilov&rft.aufirst=Anton&rft_id=https%3A%2F%2Fwww.anandtech.com%2Fshow%2F13450%2Fintels-new-core-and-xeon-w-processors-fixes-for-spectre-meltdown&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-spectreattack.com-31">^ <a href="#cite_ref-spectreattack.com_31-0">a</a> <a href="#cite_ref-spectreattack.com_31-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://spectreattack.com/">"Meltdown and Spectre"</a>. SpectreAttack.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103221345/https://spectreattack.com/">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-30.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=SpectreAttack.com&rft.atitle=Meltdown+and+Spectre&rft_id=https%3A%2F%2Fspectreattack.com%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-32"><a href="#cite_ref-32">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cybereason.com/blog/what-are-the-spectre-and-meltdown-vulnerabilities">"What Are the Spectre and Meltdown CPU Vulnerabilities"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210116172943/https://www.cybereason.com/blog/what-are-the-spectre-and-meltdown-vulnerabilities">Archived</a> from the original on 2021-01-16. Retrieved 2018-01-08.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=What+Are+the+Spectre+and+Meltdown+CPU+Vulnerabilities&rft_id=https%3A%2F%2Fwww.cybereason.com%2Fblog%2Fwhat-are-the-spectre-and-meltdown-vulnerabilities&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-meltdownwebsite-33">^ <a href="#cite_ref-meltdownwebsite_33-0">a</a> <a href="#cite_ref-meltdownwebsite_33-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://meltdownattack.com/#faq-systems-meltdown">"Meltdown and Spectre: Which systems are affected by Meltdown?"</a>. meltdownattack.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103235911/https://meltdownattack.com/#faq-systems-meltdown">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=meltdownattack.com&rft.atitle=Meltdown+and+Spectre%3A+Which+systems+are+affected+by+Meltdown%3F&rft_id=https%3A%2F%2Fmeltdownattack.com%2F%23faq-systems-meltdown&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-34"><a href="#cite_ref-34">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFSibertPorrasLindell1995" class="citation book cs1">Sibert, Olin; Porras, Philip A.; Lindell, Robert (1995-05-08). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180107190128/https://pdfs.semanticscholar.org/2209/42809262c17b6631c0f6536c91aaf7756857.pdf">"The Intel 80×86 processor architecture: Pitfalls for secure systems"</a> (PDF). Proceedings 1995 IEEE Symposium on Security and Privacy. pp. 211–222. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FSECPRI.1995.398934">10.1109/SECPRI.1995.398934</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/0-8186-7015-0" title="Special:BookSources/0-8186-7015-0"><bdi>0-8186-7015-0</bdi></a>. <a href="/wiki/S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:923198">923198</a>. Archived from <a rel="nofollow" class="external text" href="https://pdfs.semanticscholar.org/2209/42809262c17b6631c0f6536c91aaf7756857.pdf">the original</a> (PDF) on 2018-01-07. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=bookitem&rft.atitle=The+Intel+80%C3%9786+processor+architecture%3A+Pitfalls+for+secure+systems&rft.btitle=Proceedings+1995+IEEE+Symposium+on+Security+and+Privacy&rft.pages=%3Cspan+class%3D%22nowrap%22%3E211-%3C%2Fspan%3E222&rft.date=1995-05-08&rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A923198%23id-name%3DS2CID&rft_id=info%3Adoi%2F10.1109%2FSECPRI.1995.398934&rft.isbn=0-8186-7015-0&rft.aulast=Sibert&rft.aufirst=Olin&rft.au=Porras%2C+Philip+A.&rft.au=Lindell%2C+Robert&rft_id=https%3A%2F%2Fpdfs.semanticscholar.org%2F2209%2F42809262c17b6631c0f6536c91aaf7756857.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-35"><a href="#cite_ref-35">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120710081931/http://movies.apple.com/media/us/osx/2012/docs/OSX_MountainLion_Core_Technologies_Overview.pdf">"OS X Mountain Lion Core Technologies Overview"</a> (PDF). June 2012. Archived from <a rel="nofollow" class="external text" href="http://movies.apple.com/media/us/osx/2012/docs/OSX_MountainLion_Core_Technologies_Overview.pdf">the original</a> (PDF) on 2012-07-10. Retrieved 2012-07-25.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=OS+X+Mountain+Lion+Core+Technologies+Overview&rft.date=2012-06&rft_id=http%3A%2F%2Fmovies.apple.com%2Fmedia%2Fus%2Fosx%2F2012%2Fdocs%2FOSX_MountainLion_Core_Technologies_Overview.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-36"><a href="#cite_ref-36">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://kernelnewbies.org/Linux_3.14#Kernel_address_space_randomization">"Linux_3.14"</a>. kernelnewbies.org. 2017-12-30. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180119120142/https://kernelnewbies.org/Linux_3.14#Kernel_address_space_randomization">Archived</a> from the original on 2018-01-19. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=kernelnewbies.org&rft.atitle=Linux_3.14&rft.date=2017-12-30&rft_id=https%3A%2F%2Fkernelnewbies.org%2FLinux_3.14%23Kernel_address_space_randomization&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-37"><a href="#cite_ref-37">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFFoghGruss" class="citation web cs1">Fogh, Anders; Gruss, Daniel. <a rel="nofollow" class="external text" href="https://www.blackhat.com/us-16/briefings.html#anders-fogh">"Blackhat USA 2016, Using Undocumented CPU Behavior to See into Kernel Mode and Break KASLR in the Process"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180115063331/http://www.blackhat.com/us-16/briefings.html#anders-fogh">Archived</a> from the original on 2018-01-15. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Blackhat+USA+2016%2C+Using+Undocumented+CPU+Behavior+to+See+into+Kernel+Mode+and+Break+KASLR+in+the+Process&rft.aulast=Fogh&rft.aufirst=Anders&rft.au=Gruss%2C+Daniel&rft_id=https%3A%2F%2Fwww.blackhat.com%2Fus-16%2Fbriefings.html%23anders-fogh&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-38"><a href="#cite_ref-38">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFLippGrussSpreitzerMaurice2016" class="citation web cs1">Lipp, Moritz; Gruss, Daniel; Spreitzer, Raphael; Maurice, Clémentine; Mangard, Stefan (2016-08-10). <a rel="nofollow" class="external text" href="https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_lipp.pdf">"ARMageddon: Cache Attacks on Mobile Devices"</a> (PDF). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170823055023/https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_lipp.pdf">Archived</a> (PDF) from the original on 2017-08-23. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=ARMageddon%3A+Cache+Attacks+on+Mobile+Devices&rft.date=2016-08-10&rft.aulast=Lipp&rft.aufirst=Moritz&rft.au=Gruss%2C+Daniel&rft.au=Spreitzer%2C+Raphael&rft.au=Maurice%2C+Cl%C3%A9mentine&rft.au=Mangard%2C+Stefan&rft_id=https%3A%2F%2Fwww.usenix.org%2Fsystem%2Ffiles%2Fconference%2Fusenixsecurity16%2Fsec16_paper_lipp.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-39"><a href="#cite_ref-39">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFMauriceLipp2016" class="citation web cs1">Maurice, Clémentine; Lipp, Moritz (2016-12-27). <a rel="nofollow" class="external text" href="https://media.ccc.de/v/33c3-8044-what_could_possibly_go_wrong_with_insert_x86_instruction_here">"What could possibly go wrong with <insert x86 instruction here>?"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180110174530/https://media.ccc.de/v/33c3-8044-what_could_possibly_go_wrong_with_insert_x86_instruction_here">Archived</a> from the original on 2018-01-10. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=What+could+possibly+go+wrong+with+%26lt%3Binsert+x86+instruction+here%26gt%3B%3F&rft.date=2016-12-27&rft.aulast=Maurice&rft.aufirst=Cl%C3%A9mentine&rft.au=Lipp%2C+Moritz&rft_id=https%3A%2F%2Fmedia.ccc.de%2Fv%2F33c3-8044-what_could_possibly_go_wrong_with_insert_x86_instruction_here&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-40"><a href="#cite_ref-40">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFGrasRazaviBosmanBox2017" class="citation web cs1">Gras, Ben; Razavi, Kaveh; Bosman, Erik; Box, Herbert; Giuffrida, Cristiano (2017-02-27). <a rel="nofollow" class="external text" href="https://www.ndss-symposium.org/ndss2017/ndss-2017-programme/aslrcache-practical-cache-attacks-mmu/">"ASLR on the Line: Practical Cache Attacks on the MMU"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180110054846/https://www.ndss-symposium.org/ndss2017/ndss-2017-programme/aslrcache-practical-cache-attacks-mmu/">Archived</a> from the original on 2018-01-10. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=ASLR+on+the+Line%3A+Practical+Cache+Attacks+on+the+MMU&rft.date=2017-02-27&rft.aulast=Gras&rft.aufirst=Ben&rft.au=Razavi%2C+Kaveh&rft.au=Bosman%2C+Erik&rft.au=Box%2C+Herbert&rft.au=Giuffrida%2C+Cristiano&rft_id=https%3A%2F%2Fwww.ndss-symposium.org%2Fndss2017%2Fndss-2017-programme%2Faslrcache-practical-cache-attacks-mmu%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-41"><a href="#cite_ref-41">^</a> <a href="/wiki/Software_Guard_Extensions#Prime+Probe_attack" title="Software Guard Extensions">Intel SGX Prime+Probe attack</a> </li> <li id="cite_note-42"><a href="#cite_ref-42">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://gruss.cc/files/kaiser.pdf">"KASLR is Dead: Long Live KASLR"</a> (PDF). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180628101911/https://gruss.cc/files/kaiser.pdf">Archived</a> (PDF) from the original on 2018-06-28. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=KASLR+is+Dead%3A+Long+Live+KASLR&rft_id=https%3A%2F%2Fgruss.cc%2Ffiles%2Fkaiser.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-43"><a href="#cite_ref-43">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFGrussLippSchwarzFellner2017" class="citation book cs1">Gruss, Daniel; Lipp, Moritz; Schwarz, Michael; Fellner, Richard; Maurice, Clémentine; Mangard, Stefan (2017). "KASLR is Dead: Long Live KASLR". Engineering Secure Software and Systems. Lecture Notes in Computer Science. Vol. 10379. pp. 161–176. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2F978-3-319-62105-0_11">10.1007/978-3-319-62105-0_11</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/978-3-319-62104-3" title="Special:BookSources/978-3-319-62104-3"><bdi>978-3-319-62104-3</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=bookitem&rft.atitle=KASLR+is+Dead%3A+Long+Live+KASLR&rft.btitle=Engineering+Secure+Software+and+Systems&rft.series=Lecture+Notes+in+Computer+Science&rft.pages=%3Cspan+class%3D%22nowrap%22%3E161-%3C%2Fspan%3E176&rft.date=2017&rft_id=info%3Adoi%2F10.1007%2F978-3-319-62105-0_11&rft.isbn=978-3-319-62104-3&rft.aulast=Gruss&rft.aufirst=Daniel&rft.au=Lipp%2C+Moritz&rft.au=Schwarz%2C+Michael&rft.au=Fellner%2C+Richard&rft.au=Maurice%2C+Cl%C3%A9mentine&rft.au=Mangard%2C+Stefan&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-Gruss_20180103-44"><a href="#cite_ref-Gruss_20180103_44-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFGruss2018" class="citation web cs1">Gruss, Daniel (2018-01-03). <a rel="nofollow" class="external text" href="https://twitter.com/lavados/status/948536300830851072">"#FunFact: We submitted #KAISER to #bhusa17 and got it rejected"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180108013055/https://mobile.twitter.com/lavados/status/948536300830851072">Archived</a> from the original on 2018-01-08. Retrieved 2018-01-08 – via <a href="/wiki/Twitter" title="Twitter">Twitter</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=%23FunFact%3A+We+submitted+%23KAISER+to+%23bhusa17+and+got+it+rejected&rft.date=2018-01-03&rft.aulast=Gruss&rft.aufirst=Daniel&rft_id=https%3A%2F%2Ftwitter.com%2Flavados%2Fstatus%2F948536300830851072&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-MeltdownPaper-45">^ <a href="#cite_ref-MeltdownPaper_45-0">a</a> <a href="#cite_ref-MeltdownPaper_45-1">b</a> <a href="#cite_ref-MeltdownPaper_45-2">c</a> <a href="#cite_ref-MeltdownPaper_45-3">d</a> <a href="#cite_ref-MeltdownPaper_45-4">e</a> <a href="#cite_ref-MeltdownPaper_45-5">f</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFLippSchwarzGrussPrescher" class="citation web cs1">Lipp, Moritz; Schwarz, Michael; Gruss, Daniel; Prescher, Thomas; Haas, Werner; Fogh, Anders; Horn, Jann; Mangard, Stefan; <a href="/wiki/Paul_Carl_Kocher" title="Paul Carl Kocher">Kocher, Paul</a>; Genkin, Daniel; Yarom, Yuval; Hamburg, Mike. <a rel="nofollow" class="external text" href="https://meltdownattack.com/meltdown.pdf">"Meltdown: Reading Kernel Memory from User Space"</a> (PDF). MeltdownAttack.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104180746/https://meltdownattack.com/meltdown.pdf">Archived</a> (PDF) from the original on 2018-01-04. Retrieved 2019-02-25.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=MeltdownAttack.com&rft.atitle=Meltdown%3A+Reading+Kernel+Memory+from+User+Space&rft.aulast=Lipp&rft.aufirst=Moritz&rft.au=Schwarz%2C+Michael&rft.au=Gruss%2C+Daniel&rft.au=Prescher%2C+Thomas&rft.au=Haas%2C+Werner&rft.au=Fogh%2C+Anders&rft.au=Horn%2C+Jann&rft.au=Mangard%2C+Stefan&rft.au=Kocher%2C+Paul&rft.au=Genkin%2C+Daniel&rft.au=Yarom%2C+Yuval&rft.au=Hamburg%2C+Mike&rft_id=https%3A%2F%2Fmeltdownattack.com%2Fmeltdown.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-46"><a href="#cite_ref-46">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/">"Negative Result Reading Kernel Memory from user Mode"</a>. 2017-07-28. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180105211148/https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/">Archived</a> from the original on 2018-01-05. Retrieved 2018-01-06.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Negative+Result+Reading+Kernel+Memory+from+user+Mode&rft.date=2017-07-28&rft_id=https%3A%2F%2Fcyber.wtf%2F2017%2F07%2F28%2Fnegative-result-reading-kernel-memory-from-user-mode%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-47"><a href="#cite_ref-47">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://blog.netbsd.org/tnf/entry/kernel_aslr_on_amd64">"Kernel ASLR on amd64"</a>. 2017. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171016175156/https://blog.netbsd.org/tnf/entry/kernel_aslr_on_amd64">Archived</a> from the original on 2017-10-16. Retrieved 2017-10-16.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Kernel+ASLR+on+amd64&rft.date=2017&rft_id=https%3A%2F%2Fblog.netbsd.org%2Ftnf%2Fentry%2Fkernel_aslr_on_amd64&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-48"><a href="#cite_ref-48">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://opensource.apple.com/">"Apple Open Source"</a>. 2017. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200917011846/https://opensource.apple.com/">Archived</a> from the original on 2020-09-17. Retrieved 2018-01-13.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Apple+Open+Source&rft.date=2017&rft_id=http%3A%2F%2Fopensource.apple.com%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-Ionescu_20171114-49"><a href="#cite_ref-Ionescu_20171114_49-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFIonescu2017" class="citation web cs1">Ionescu, Alex (2017-11-14). <a rel="nofollow" class="external text" href="https://twitter.com/aionescu/status/930412525111296000">"Windows 17035 Kernel ASLR/VA Isolation In Practice (like Linux KAISER)"</a>. <a href="/wiki/Twitter" title="Twitter">Twitter</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180106120141/https://mobile.twitter.com/aionescu/status/930412525111296000">Archived</a> from the original on 2018-01-06. Retrieved 2018-01-06.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Twitter&rft.atitle=Windows+17035+Kernel+ASLR%2FVA+Isolation+In+Practice+%28like+Linux+KAISER%29&rft.date=2017-11-14&rft.aulast=Ionescu&rft.aufirst=Alex&rft_id=https%3A%2F%2Ftwitter.com%2Faionescu%2Fstatus%2F930412525111296000&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-Gibbs_20180104-50"><a href="#cite_ref-Gibbs_20180104_50-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFGibbs2018" class="citation news cs1">Gibbs, Samuel (2018-01-04). <a rel="nofollow" class="external text" href="https://www.theguardian.com/technology/2018/jan/04/meltdown-spectre-worst-cpu-bugs-ever-found-affect-computers-intel-processors-security-flaw">"Meltdown and Spectre: 'worst ever' CPU bugs affect virtually all computers"</a>. The Guardian. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180106114401/https://www.theguardian.com/technology/2018/jan/04/meltdown-spectre-worst-cpu-bugs-ever-found-affect-computers-intel-processors-security-flaw">Archived</a> from the original on 2018-01-06. Retrieved 2018-01-06.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=The+Guardian&rft.atitle=Meltdown+and+Spectre%3A+%27worst+ever%27+CPU+bugs+affect+virtually+all+computers&rft.date=2018-01-04&rft.aulast=Gibbs&rft.aufirst=Samuel&rft_id=https%3A%2F%2Fwww.theguardian.com%2Ftechnology%2F2018%2Fjan%2F04%2Fmeltdown-spectre-worst-cpu-bugs-ever-found-affect-computers-intel-processors-security-flaw&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-51"><a href="#cite_ref-51">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown">"Information Leak via speculative execution side channel attacks (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754 aka Spectre and Meltdown)"</a>. Ubuntu Wiki. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104191555/https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Ubuntu+Wiki&rft.atitle=Information+Leak+via+speculative+execution+side+channel+attacks+%28CVE-2017-5715%2C+CVE-2017-5753%2C+CVE-2017-5754+aka+Spectre+and+Meltdown%29&rft_id=https%3A%2F%2Fwiki.ubuntu.com%2FSecurityTeam%2FKnowledgeBase%2FSpectreAndMeltdown&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-TC-20180128-52"><a href="#cite_ref-TC-20180128_52-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFLynley2018" class="citation web cs1">Lynley, Matthew (2018-01-28). <a rel="nofollow" class="external text" href="https://techcrunch.com/2018/01/28/intel-reportedly-notified-chinese-companies-of-chip-security-flaw-before-the-u-s-government/">"Intel reportedly notified Chinese companies of chip security flaw before the U.S. government"</a>. <a href="/wiki/TechCrunch" title="TechCrunch">TechCrunch</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180216155611/https://techcrunch.com/2018/01/28/intel-reportedly-notified-chinese-companies-of-chip-security-flaw-before-the-u-s-government/">Archived</a> from the original on 2018-02-16. Retrieved 2018-01-28.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=TechCrunch&rft.atitle=Intel+reportedly+notified+Chinese+companies+of+chip+security+flaw+before+the+U.S.+government&rft.date=2018-01-28&rft.aulast=Lynley&rft.aufirst=Matthew&rft_id=https%3A%2F%2Ftechcrunch.com%2F2018%2F01%2F28%2Fintel-reportedly-notified-chinese-companies-of-chip-security-flaw-before-the-u-s-government%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-zdnet-nov2018-53"><a href="#cite_ref-zdnet-nov2018_53-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFCatalin_Cimpanu2018" class="citation news cs1">Catalin Cimpanu (2018-11-14). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/researchers-discover-seven-new-meltdown-and-spectre-attacks/">"Researchers discover seven new Meltdown and Spectre attacks"</a>. <a href="/wiki/ZDNet" class="mw-redirect" title="ZDNet">ZDNet</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20181116183149/https://www.zdnet.com/article/researchers-discover-seven-new-meltdown-and-spectre-attacks/">Archived</a> from the original on 2018-11-16. Retrieved 2018-11-17.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=ZDNet&rft.atitle=Researchers+discover+seven+new+Meltdown+and+Spectre+attacks&rft.date=2018-11-14&rft.au=Catalin+Cimpanu&rft_id=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fresearchers-discover-seven-new-meltdown-and-spectre-attacks%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-Galowicz_Jan_3_2018-54">^ <a href="#cite_ref-Galowicz_Jan_3_2018_54-0">a</a> <a href="#cite_ref-Galowicz_Jan_3_2018_54-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFGalowicz2018" class="citation web cs1">Galowicz, Jacek (2018-01-03). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104094258/http://blog.cyberus-technology.de/posts/2018-01-03-meltdown.html">"Cyberus Technology Blog – Meltdown"</a>. blog.cyberus-technology.de. Archived from <a rel="nofollow" class="external text" href="http://blog.cyberus-technology.de/posts/2018-01-03-meltdown.html">the original</a> on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=blog.cyberus-technology.de&rft.atitle=Cyberus+Technology+Blog+%E2%80%93+Meltdown&rft.date=2018-01-03&rft.aulast=Galowicz&rft.aufirst=Jacek&rft_id=http%3A%2F%2Fblog.cyberus-technology.de%2Fposts%2F2018-01-03-meltdown.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-Wheeler_Jan_4_2018-55"><a href="#cite_ref-Wheeler_Jan_4_2018_55-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFWheeler2018" class="citation web cs1">Wheeler, Eric (2018-01-04). <a rel="nofollow" class="external text" href="https://www.linuxglobal.com/meltdown-bug-affected-virtualization-technologies/">"Meltdown BUG: What about KVM/Xen/Docker/OpenVZ/LXC/PV-Xen/HyperV?"</a>. linuxglobal.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180106173909/https://www.linuxglobal.com/meltdown-bug-affected-virtualization-technologies/">Archived</a> from the original on 2018-01-06. Retrieved 2018-01-06.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=linuxglobal.com&rft.atitle=Meltdown+BUG%3A+What+about+KVM%2FXen%2FDocker%2FOpenVZ%2FLXC%2FPV-Xen%2FHyperV%3F&rft.date=2018-01-04&rft.aulast=Wheeler&rft.aufirst=Eric&rft_id=https%3A%2F%2Fwww.linuxglobal.com%2Fmeltdown-bug-affected-virtualization-technologies%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-56"><a href="#cite_ref-56">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFBhat2018" class="citation web cs1">Bhat, Akshay (2018-01-17). <a rel="nofollow" class="external text" href="https://www.timesys.com/security/meltdown-spectre-vulnerabilities/">"Meltdown and Spectre vulnerabilities"</a>. timesys.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180126071017/https://www.timesys.com/security/meltdown-spectre-vulnerabilities/">Archived</a> from the original on 2018-01-26. Retrieved 2018-01-23. <q>unless your product allows running 3rd party or WEB applications, we believe the device is not exposed to exploits</q></cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=timesys.com&rft.atitle=Meltdown+and+Spectre+vulnerabilities&rft.date=2018-01-17&rft.aulast=Bhat&rft.aufirst=Akshay&rft_id=https%3A%2F%2Fwww.timesys.com%2Fsecurity%2Fmeltdown-spectre-vulnerabilities%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-Intel-20180103-57"><a href="#cite_ref-Intel-20180103_57-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFStaff2018" class="citation web cs1">Staff (2018-01-03). <a rel="nofollow" class="external text" href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/">"Intel Responds To Security Research Findings"</a>. <a href="/wiki/Intel" title="Intel">Intel</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103211746/https://newsroom.intel.com/news/intel-responds-to-security-research-findings/">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Intel&rft.atitle=Intel+Responds+To+Security+Research+Findings&rft.date=2018-01-03&rft.au=Staff&rft_id=https%3A%2F%2Fnewsroom.intel.com%2Fnews%2Fintel-responds-to-security-research-findings%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-58"><a href="#cite_ref-58">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://aws.amazon.com/de/security/security-bulletins/AWS-2018-013/">"Processor Speculative Execution Research Disclosure"</a>. Amazon Web Services, Inc. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104002733/https://aws.amazon.com/de/security/security-bulletins/AWS-2018-013/">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Amazon+Web+Services%2C+Inc.&rft.atitle=Processor+Speculative+Execution+Research+Disclosure&rft_id=https%3A%2F%2Faws.amazon.com%2Fde%2Fsecurity%2Fsecurity-bulletins%2FAWS-2018-013%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-59"><a href="#cite_ref-59">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation magazine cs1"><a rel="nofollow" class="external text" href="https://www.wired.com/story/critical-intel-flaw-breaks-basic-security-for-most-computers/">"A Critical Intel Flaw Breaks Basic Security for Most Computers"</a>. Wired. 2018-01-03. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103204011/https://www.wired.com/story/critical-intel-flaw-breaks-basic-security-for-most-computers/">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Wired&rft.atitle=A+Critical+Intel+Flaw+Breaks+Basic+Security+for+Most+Computers&rft.date=2018-01-03&rft_id=https%3A%2F%2Fwww.wired.com%2Fstory%2Fcritical-intel-flaw-breaks-basic-security-for-most-computers%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-ARM_Security_Update-60">^ <a href="#cite_ref-ARM_Security_Update_60-0">a</a> <a href="#cite_ref-ARM_Security_Update_60-1">b</a> <a href="#cite_ref-ARM_Security_Update_60-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://developer.arm.com/support/security-update">"Arm Processor Security Update"</a>. ARM Developer. <a href="/wiki/ARM_Ltd." class="mw-redirect" title="ARM Ltd.">ARM Ltd.</a> 2018-01-03. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180404110048/https://developer.arm.com/support/security-update">Archived</a> from the original on 2018-04-04. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=ARM+Developer&rft.atitle=Arm+Processor+Security+Update&rft.date=2018-01-03&rft_id=https%3A%2F%2Fdeveloper.arm.com%2Fsupport%2Fsecurity-update&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-61"><a href="#cite_ref-61">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.theverge.com/2018/1/3/16844630/intel-processor-security-flaw-bug-kernel-windows-linux">"Intel's processors have a security bug and the fix could slow down PCs"</a>. <a href="/wiki/The_Verge" title="The Verge">The Verge</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103141306/https://www.theverge.com/2018/1/3/16844630/intel-processor-security-flaw-bug-kernel-windows-linux">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=The+Verge&rft.atitle=Intel%27s+processors+have+a+security+bug+and+the+fix+could+slow+down+PCs&rft_id=https%3A%2F%2Fwww.theverge.com%2F2018%2F1%2F3%2F16844630%2Fintel-processor-security-flaw-bug-kernel-windows-linux&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-auto-62">^ <a href="#cite_ref-auto_62-0">a</a> <a href="#cite_ref-auto_62-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.phoronix.com/scan.php?page=news_item&px=x86-PTI-Initial-Gaming-Tests">"Linux Gaming Performance Doesn't Appear Affected By The x86 PTI Work"</a>. Phoronix.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210220121617/https://www.phoronix.com/scan.php?page=news_item&px=x86-PTI-Initial-Gaming-Tests">Archived</a> from the original on 2021-02-20. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Phoronix.com&rft.atitle=Linux+Gaming+Performance+Doesn%27t+Appear+Affected+By+The+x86+PTI+Work&rft_id=https%3A%2F%2Fwww.phoronix.com%2Fscan.php%3Fpage%3Dnews_item%26px%3Dx86-PTI-Initial-Gaming-Tests&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-63"><a href="#cite_ref-63">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFLendacky" class="citation web cs1">Lendacky, Tom. <a rel="nofollow" class="external text" href="https://lkml.org/lkml/2018/1/3/425">"[tip:x86/pti] x86/cpu, x86/pti: Do not enable PTI on AMD processors"</a>. LKML.org. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200803220216/https://lkml.org/lkml/2018/1/3/425">Archived</a> from the original on 2020-08-03. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=LKML.org&rft.atitle=%5Btip%3Ax86%2Fpti%5D+x86%2Fcpu%2C+x86%2Fpti%3A+Do+not+enable+PTI+on+AMD+processors&rft.aulast=Lendacky&rft.aufirst=Tom&rft_id=https%3A%2F%2Flkml.org%2Flkml%2F2018%2F1%2F3%2F425&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-64"><a href="#cite_ref-64">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.digitaltrends.com/computing/intel-cpus-suffer-bug-requiring-performance-reducing-fix/">"Patches arrive for Intel's 'Meltdown' flaw — here's how to protect your device"</a>. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180109144903/https://www.digitaltrends.com/computing/intel-cpus-suffer-bug-requiring-performance-reducing-fix/">Archived</a> from the original on 2018-01-09. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Patches+arrive+for+Intel%27s+%27Meltdown%27+flaw+%E2%80%94+here%27s+how+to+protect+your+device&rft.date=2018-01-04&rft_id=https%3A%2F%2Fwww.digitaltrends.com%2Fcomputing%2Fintel-cpus-suffer-bug-requiring-performance-reducing-fix%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-65"><a href="#cite_ref-65">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.amd.com/en/corporate/speculative-execution">"An Update on AMD Processor Security"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104014617/https://www.amd.com/en/corporate/speculative-execution">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-29.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=An+Update+on+AMD+Processor+Security&rft_id=https%3A%2F%2Fwww.amd.com%2Fen%2Fcorporate%2Fspeculative-execution&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-66"><a href="#cite_ref-66">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104214625/http://chronicle.augusta.com/news/business/2018-01-04/who-s-affected-computer-chip-security-flaw">"Who's affected by computer chip security flaw"</a>. Archived from <a rel="nofollow" class="external text" href="http://chronicle.augusta.com/news/business/2018-01-04/who-s-affected-computer-chip-security-flaw">the original</a> on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Who%27s+affected+by+computer+chip+security+flaw&rft_id=http%3A%2F%2Fchronicle.augusta.com%2Fnews%2Fbusiness%2F2018-01-04%2Fwho-s-affected-computer-chip-security-flaw&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-67"><a href="#cite_ref-67">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/">"Kernel-memory-leaking Intel processor design flaw forces Linux, Windows redesign"</a>. <a href="/wiki/The_Register" title="The Register">The Register</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180407091509/http://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/">Archived</a> from the original on 2018-04-07. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=The+Register&rft.atitle=Kernel-memory-leaking+Intel+processor+design+flaw+forces+Linux%2C+Windows+redesign&rft_id=https%3A%2F%2Fwww.theregister.co.uk%2F2018%2F01%2F02%2Fintel_cpu_design_flaw%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-68"><a href="#cite_ref-68">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFStaff2018" class="citation web cs1">Staff (2018). <a rel="nofollow" class="external text" href="https://spectreattack.com/#faq-systems-spectre">"Meltdown and Spectre-faq-systems-spectre"</a>. <a href="/wiki/Graz_University_of_Technology" title="Graz University of Technology">Graz University of Technology</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103221345/https://spectreattack.com/#faq-systems-spectre">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Graz+University+of+Technology&rft.atitle=Meltdown+and+Spectre-faq-systems-spectre&rft.date=2018&rft.au=Staff&rft_id=https%3A%2F%2Fspectreattack.com%2F%23faq-systems-spectre&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-69"><a href="#cite_ref-69">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="busvined_nelliss" class="citation web cs1">Busvine, Douglas; Nellis, Stephen (2018-01-03). <a rel="nofollow" class="external text" href="https://www.reuters.com/article/us-cyber-intel/security-flaws-put-virtually-all-phones-computers-at-risk-idUSKBN1ES1BO">"Security flaws put virtually all phones, computers at risk"</a>. Reuters. Thomson-Reuters. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103232451/https://www.reuters.com/article/us-cyber-intel/security-flaws-put-virtually-all-phones-computers-at-risk-idUSKBN1ES1BO">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-08.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Reuters&rft.atitle=Security+flaws+put+virtually+all+phones%2C+computers+at+risk&rft.date=2018-01-03&rft.aulast=Busvine&rft.aufirst=Douglas&rft.au=Nellis%2C+Stephen&rft_id=https%3A%2F%2Fwww.reuters.com%2Farticle%2Fus-cyber-intel%2Fsecurity-flaws-put-virtually-all-phones-computers-at-risk-idUSKBN1ES1BO&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-70"><a href="#cite_ref-70">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.bleepingcomputer.com/news/security/google-almost-all-cpus-since-1995-vulnerable-to-meltdown-and-spectre-flaws/">"Google: Almost All CPUs Since 1995 Vulnerable To "Meltdown" And "Spectre" Flaws"</a>. BleepingComputer. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210420211135/https://www.bleepingcomputer.com/news/security/google-almost-all-cpus-since-1995-vulnerable-to-meltdown-and-spectre-flaws/">Archived</a> from the original on 2021-04-20. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=BleepingComputer&rft.atitle=Google%3A+Almost+All+CPUs+Since+1995+Vulnerable+To+%22Meltdown%22+And+%22Spectre%22+Flaws&rft_id=https%3A%2F%2Fwww.bleepingcomputer.com%2Fnews%2Fsecurity%2Fgoogle-almost-all-cpus-since-1995-vulnerable-to-meltdown-and-spectre-flaws%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-71"><a href="#cite_ref-71">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.jaist.ac.jp/iscenter-new/mpc/altix/altixdata/opt/intel/vtune/doc/users_guide/mergedProjects/analyzer_ec/mergedProjects/reference_olh/reference_hh/p6_family_micro-architecture.htm">"P6 family microarchitecture"</a>. jaist.ac.jp. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200103032735/http://www.jaist.ac.jp/iscenter-new/mpc/altix/altixdata/opt/intel/vtune/doc/users_guide/mergedProjects/analyzer_ec/mergedProjects/reference_olh/reference_hh/p6_family_micro-architecture.htm">Archived</a> from the original on 2020-01-03. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=jaist.ac.jp&rft.atitle=P6+family+microarchitecture&rft_id=http%3A%2F%2Fwww.jaist.ac.jp%2Fiscenter-new%2Fmpc%2Faltix%2Faltixdata%2Fopt%2Fintel%2Fvtune%2Fdoc%2Fusers_guide%2FmergedProjects%2Fanalyzer_ec%2FmergedProjects%2Freference_olh%2Freference_hh%2Fp6_family_micro-architecture.htm&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-72"><a href="#cite_ref-72">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://fortune.com/2018/01/04/meltdown-spectre-intel-amd-arm-security-bug-apple-microsoft-google-apple-amazon/">"Understanding Those Alarming Computer Chip Security Holes: 'Meltdown' and 'Spectre'"</a>. Fortune. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240521072017/https://fortune.com/2018/01/04/meltdown-spectre-intel-amd-arm-security-bug-apple-microsoft-google-apple-amazon/">Archived</a> from the original on 2024-05-21. Retrieved 2024-05-21.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Fortune&rft.atitle=Understanding+Those+Alarming+Computer+Chip+Security+Holes%3A+%27Meltdown%27+and+%27Spectre%27&rft_id=https%3A%2F%2Ffortune.com%2F2018%2F01%2F04%2Fmeltdown-spectre-intel-amd-arm-security-bug-apple-microsoft-google-apple-amazon%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-73"><a href="#cite_ref-73">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.androidauthority.com/meltdown-spectre-kpti-827527/">"'Spectre' and 'Meltdown': New CPU vulnerabilities affect most smartphones and computers"</a>. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200927092026/https://www.androidauthority.com/meltdown-spectre-kpti-827527/">Archived</a> from the original on 2020-09-27. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=%27Spectre%27+and+%27Meltdown%27%3A+New+CPU+vulnerabilities+affect+most+smartphones+and+computers&rft.date=2018-01-04&rft_id=https%3A%2F%2Fwww.androidauthority.com%2Fmeltdown-spectre-kpti-827527%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-74"><a href="#cite_ref-74">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/">"Why Raspberry Pi Isn't Vulnerable to Spectre or Meltdown"</a>. Raspberry Pi. 2018-01-05. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210409095735/https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/">Archived</a> from the original on 2021-04-09. Retrieved 2018-01-30.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Why+Raspberry+Pi+Isn%27t+Vulnerable+to+Spectre+or+Meltdown&rft.pub=Raspberry+Pi&rft.date=2018-01-05&rft_id=https%3A%2F%2Fwww.raspberrypi.org%2Fblog%2Fwhy-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-75"><a href="#cite_ref-75">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFTung2018" class="citation news cs1">Tung, Liam (2018-01-10). <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/meltdown-spectre-ibm-preps-firmware-and-os-fixes-for-vulnerable-power-cpus/">"Meltdown-Spectre: IBM preps firmware and OS fixes for vulnerable Power CPUs"</a>. ZDNet. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200803205205/https://www.zdnet.com/article/meltdown-spectre-ibm-preps-firmware-and-os-fixes-for-vulnerable-power-cpus/">Archived</a> from the original on 2020-08-03. Retrieved 2018-01-30.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=ZDNet&rft.atitle=Meltdown-Spectre%3A+IBM+preps+firmware+and+OS+fixes+for+vulnerable+Power+CPUs&rft.date=2018-01-10&rft.aulast=Tung&rft.aufirst=Liam&rft_id=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fmeltdown-spectre-ibm-preps-firmware-and-os-fixes-for-vulnerable-power-cpus%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-76"><a href="#cite_ref-76">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://talesfromthedatacenter.com/2018/01/solarissparc-is-meltdown-cve-2017-5754-free/">"Solaris+SPARC is Meltdown (CVE-2017-5754) free – Tales from the Datacenter"</a>. Tales from the Datacenter. 2018-01-22. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210709181624/https://talesfromthedatacenter.com/2018/01/solarissparc-is-meltdown-cve-2017-5754-free/">Archived</a> from the original on 2021-07-09. Retrieved 2018-01-23.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Tales+from+the+Datacenter&rft.atitle=Solaris%2BSPARC+is+Meltdown+%28CVE-2017-5754%29+free+%E2%80%93+Tales+from+the+Datacenter&rft.date=2018-01-22&rft_id=https%3A%2F%2Ftalesfromthedatacenter.com%2F2018%2F01%2Fsolarissparc-is-meltdown-cve-2017-5754-free%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-77"><a href="#cite_ref-77">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFKroah-Hartman2018" class="citation web cs1">Kroah-Hartman, Greg (2018-01-02). <a rel="nofollow" class="external text" href="https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.11">"Linux 4.14.11 Changelog"</a>. kernel.org. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103160126/https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.11">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-06.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=kernel.org&rft.atitle=Linux+4.14.11+Changelog&rft.date=2018-01-02&rft.aulast=Kroah-Hartman&rft.aufirst=Greg&rft_id=https%3A%2F%2Fcdn.kernel.org%2Fpub%2Flinux%2Fkernel%2Fv4.x%2FChangeLog-4.14.11&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-78"><a href="#cite_ref-78">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFKroah-Hartman2018" class="citation web cs1">Kroah-Hartman, Greg (2018-01-05). <a rel="nofollow" class="external text" href="https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.75">"Linux 4.9.75 Changelog"</a>. kernel.org. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180106120351/https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.75">Archived</a> from the original on 2018-01-06. Retrieved 2018-01-06.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=kernel.org&rft.atitle=Linux+4.9.75+Changelog&rft.date=2018-01-05&rft.aulast=Kroah-Hartman&rft.aufirst=Greg&rft_id=https%3A%2F%2Fcdn.kernel.org%2Fpub%2Flinux%2Fkernel%2Fv4.x%2FChangeLog-4.9.75&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-79"><a href="#cite_ref-79">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFCorbet2017" class="citation web cs1">Corbet, Jonathon (2017-11-15). <a rel="nofollow" class="external text" href="https://lwn.net/Articles/738975/">"KAISER: hiding the kernel from user space"</a>. LWN. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201208004347/https://lwn.net/Articles/738975/">Archived</a> from the original on 2020-12-08. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=LWN&rft.atitle=KAISER%3A+hiding+the+kernel+from+user+space&rft.date=2017-11-15&rft.aulast=Corbet&rft.aufirst=Jonathon&rft_id=https%3A%2F%2Flwn.net%2FArticles%2F738975%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-80"><a href="#cite_ref-80">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFCorbet2017" class="citation web cs1">Corbet, Jonathon (2017-12-20). <a rel="nofollow" class="external text" href="https://lwn.net/Articles/741878/">"The current state of kernel page-table isolation"</a>. LWN. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104192446/https://lwn.net/Articles/741878/">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=LWN&rft.atitle=The+current+state+of+kernel+page-table+isolation&rft.date=2017-12-20&rft.aulast=Corbet&rft.aufirst=Jonathon&rft_id=https%3A%2F%2Flwn.net%2FArticles%2F741878%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-81"><a href="#cite_ref-81">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://access.redhat.com/errata/RHSA-2018:0008">"RHSA-2018:0008 – Security Advisory"</a>. RedHat announcements. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104141316/https://access.redhat.com/errata/RHSA-2018:0008">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=RedHat+announcements&rft.atitle=RHSA-2018%3A0008+%E2%80%93+Security+Advisory&rft_id=https%3A%2F%2Faccess.redhat.com%2Ferrata%2FRHSA-2018%3A0008&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-82"><a href="#cite_ref-82">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://access.redhat.com/errata/RHSA-2018:0007">"RHSA-2018:0007 – Security Advisory"</a>. RedHat announcements. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104164721/https://access.redhat.com/errata/RHSA-2018:0007">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=RedHat+announcements&rft.atitle=RHSA-2018%3A0007+%E2%80%93+Security+Advisory&rft_id=https%3A%2F%2Faccess.redhat.com%2Ferrata%2FRHSA-2018%3A0007&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-83"><a href="#cite_ref-83">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html">"[CentOS-announce] CESA-2018:0008 Important CentOS 6 kernel Security Update"</a>. CentOS announcements. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180105123201/https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html">Archived</a> from the original on 2018-01-05. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=CentOS+announcements&rft.atitle=%5BCentOS-announce%5D+CESA-2018%3A0008+Important+CentOS+6+kernel+Security+Update&rft.date=2018-01-04&rft_id=https%3A%2F%2Flists.centos.org%2Fpipermail%2Fcentos-announce%2F2018-January%2F022701.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-84"><a href="#cite_ref-84">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://lists.centos.org/pipermail/centos-announce/2018-January/022696.html">"[CentOS-announce] CESA-2018:0007 Important CentOS 7 kernel Security Update"</a>. CentOS announcements. 2018-01-04. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180105011923/https://lists.centos.org/pipermail/centos-announce/2018-January/022696.html">Archived</a> from the original on 2018-01-05. Retrieved 2018-01-05.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=CentOS+announcements&rft.atitle=%5BCentOS-announce%5D+CESA-2018%3A0007+Important+CentOS+7+kernel+Security+Update&rft.date=2018-01-04&rft_id=https%3A%2F%2Flists.centos.org%2Fpipermail%2Fcentos-announce%2F2018-January%2F022696.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-:0-85"><a href="#cite_ref-:0_85-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/">"Kernel-memory-leaking Intel processor design flaw forces Linux, Windows redesign"</a>. <a href="/wiki/The_Register" title="The Register">The Register</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180407091509/http://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/">Archived</a> from the original on 2018-04-07. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=The+Register&rft.atitle=Kernel-memory-leaking+Intel+processor+design+flaw+forces+Linux%2C+Windows+redesign&rft_id=https%3A%2F%2Fwww.theregister.co.uk%2F2018%2F01%2F02%2Fintel_cpu_design_flaw%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-86"><a href="#cite_ref-86">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208331">"About the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180111041855/https://support.apple.com/en-us/HT208331">Archived</a> from the original on 2018-01-11. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Apple+Support&rft.atitle=About+the+security+content+of+macOS+High+Sierra+10.13.2%2C+Security+Update+2017-002+Sierra%2C+and+Security+Update+2017-005+El+Capitan&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208331&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-87"><a href="#cite_ref-87">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208334">"About the security content of iOS 11.2"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171206192107/https://support.apple.com/en-us/HT208334">Archived</a> from the original on 2017-12-06. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Apple+Support&rft.atitle=About+the+security+content+of+iOS+11.2&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208334&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-88"><a href="#cite_ref-88">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208327">"About the security content of tvOS 11.2"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180118122826/https://support.apple.com/en-us/HT208327">Archived</a> from the original on 2018-01-18. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Apple+Support&rft.atitle=About+the+security+content+of+tvOS+11.2&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208327&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-89"><a href="#cite_ref-89">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208394">"About speculative execution vulnerabilities in ARM-based and Intel CPUs"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210327083711/https://support.apple.com/en-us/HT208394">Archived</a> from the original on 2021-03-27. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Apple+Support&rft.atitle=About+speculative+execution+vulnerabilities+in+ARM-based+and+Intel+CPUs&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208394&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-90"><a href="#cite_ref-90">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.macrumors.com/2018/01/08/macos-high-sierra-10-13-2-spectre-fix/">"Apple Releases macOS High Sierra 10.13.2 Supplemental Update With Spectre Fix"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180118122622/https://www.macrumors.com/2018/01/08/macos-high-sierra-10-13-2-spectre-fix/">Archived</a> from the original on 2018-01-18. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.atitle=Apple+Releases+macOS+High+Sierra+10.13.2+Supplemental+Update+With+Spectre+Fix&rft_id=https%3A%2F%2Fwww.macrumors.com%2F2018%2F01%2F08%2Fmacos-high-sierra-10-13-2-spectre-fix%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-91"><a href="#cite_ref-91">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.macrumors.com/2018/01/08/apple-releases-ios-11-2-2-with-spectre-fix/">"Apple Releases iOS 11.2.2 With Security Fixes to Address Spectre Vulnerability"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180118013303/https://www.macrumors.com/2018/01/08/apple-releases-ios-11-2-2-with-spectre-fix/">Archived</a> from the original on 2018-01-18. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.atitle=Apple+Releases+iOS+11.2.2+With+Security+Fixes+to+Address+Spectre+Vulnerability&rft_id=https%3A%2F%2Fwww.macrumors.com%2F2018%2F01%2F08%2Fapple-releases-ios-11-2-2-with-spectre-fix%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-92"><a href="#cite_ref-92">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208403">"About the security content of Safari 11.0.2"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180117150153/https://support.apple.com/en-us/HT208403">Archived</a> from the original on 2018-01-17. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Apple+Support&rft.atitle=About+the+security+content+of+Safari+11.0.2&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208403&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-93"><a href="#cite_ref-93">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208397">"About the security content of macOS High Sierra 10.13.2 Supplemental Update"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180111183509/https://support.apple.com/en-us/HT208397">Archived</a> from the original on 2018-01-11. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Apple+Support&rft.atitle=About+the+security+content+of+macOS+High+Sierra+10.13.2+Supplemental+Update&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208397&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-94"><a href="#cite_ref-94">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://support.apple.com/en-us/HT208401">"About the security content of iOS 11.2.2"</a>. Apple Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180109030407/https://support.apple.com/en-us/HT208401">Archived</a> from the original on 2018-01-09. Retrieved 2018-01-18.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Apple+Support&rft.atitle=About+the+security+content+of+iOS+11.2.2&rft_id=https%3A%2F%2Fsupport.apple.com%2Fen-us%2FHT208401&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-95"><a href="#cite_ref-95">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="warrent_010318" class="citation web cs1">Warren, Tom (2018-01-03). <a rel="nofollow" class="external text" href="https://www.theverge.com/2018/1/3/16846784/microsoft-processor-bug-windows-10-fix">"Microsoft issues emergency Windows update for processor security bugs"</a>. The Verge. <a href="/wiki/Vox_Media,_Inc." class="mw-redirect" title="Vox Media, Inc.">Vox Media, Inc.</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103215148/https://www.theverge.com/2018/1/3/16846784/microsoft-processor-bug-windows-10-fix">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=The+Verge&rft.atitle=Microsoft+issues+emergency+Windows+update+for+processor+security+bugs&rft.date=2018-01-03&rft.aulast=Warren&rft.aufirst=Tom&rft_id=https%3A%2F%2Fwww.theverge.com%2F2018%2F1%2F3%2F16846784%2Fmicrosoft-processor-bug-windows-10-fix&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-96"><a href="#cite_ref-96">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFThorp-Lancaster2018" class="citation web cs1">Thorp-Lancaster, Dan (2018-01-03). <a rel="nofollow" class="external text" href="https://www.windowscentral.com/microsoft-pushing-out-emergency-fix-newly-disclosed-processor-exploit">"Microsoft pushing out emergency fix for newly disclosed processor exploit"</a>. Windows Central. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104085324/https://www.windowscentral.com/microsoft-pushing-out-emergency-fix-newly-disclosed-processor-exploit">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Windows+Central&rft.atitle=Microsoft+pushing+out+emergency+fix+for+newly+disclosed+processor+exploit&rft.date=2018-01-03&rft.aulast=Thorp-Lancaster&rft.aufirst=Dan&rft_id=https%3A%2F%2Fwww.windowscentral.com%2Fmicrosoft-pushing-out-emergency-fix-newly-disclosed-processor-exploit&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-97"><a href="#cite_ref-97">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.microsoft.com/en-gb/help/4073119/windows-client-guidance-for-it-pros-to-protect-against-speculative-exe">"Windows Client Guidance for IT Pros to protect against speculative execution side-channel vulnerabilities"</a>. support.microsoft.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104225205/https://support.microsoft.com/en-gb/help/4073119/windows-client-guidance-for-it-pros-to-protect-against-speculative-exe">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=support.microsoft.com&rft.atitle=Windows+Client+Guidance+for+IT+Pros+to+protect+against+speculative+execution+side-channel+vulnerabilities&rft_id=https%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F4073119%2Fwindows-client-guidance-for-it-pros-to-protect-against-speculative-exe&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-98"><a href="#cite_ref-98">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.microsoft.com/en-us/help/4072698/windows-server-guidance-to-protect-against-the-speculative-execution-s">"Windows Server Guidance to protect against the speculative execution side-channel vulnerabilities"</a>. Microsoft Support. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104170752/https://support.microsoft.com/en-us/help/4072698/windows-server-guidance-to-protect-against-the-speculative-execution-s">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Microsoft+Support&rft.atitle=Windows+Server+Guidance+to+protect+against+the+speculative+execution+side-channel+vulnerabilities&rft_id=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4072698%2Fwindows-server-guidance-to-protect-against-the-speculative-execution-s&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-msamdissue-zdnet-99">^ <a href="#cite_ref-msamdissue-zdnet_99-0">a</a> <a href="#cite_ref-msamdissue-zdnet_99-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFRanger" class="citation news cs1">Ranger, Steve. <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/meltdown-and-spectre-now-microsoft-blocks-security-updates-for-some-amd-based-devices/">"Windows Meltdown and Spectre patches: Now Microsoft blocks security updates for some AMD based PCs"</a>. ZDNet. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180112140005/https://www.zdnet.com/article/meltdown-and-spectre-now-microsoft-blocks-security-updates-for-some-amd-based-devices/">Archived</a> from the original on 2018-01-12. Retrieved 2018-01-09.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=ZDNet&rft.atitle=Windows+Meltdown+and+Spectre+patches%3A+Now+Microsoft+blocks+security+updates+for+some+AMD+based+PCs&rft.aulast=Ranger&rft.aufirst=Steve&rft_id=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fmeltdown-and-spectre-now-microsoft-blocks-security-updates-for-some-amd-based-devices%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-100"><a href="#cite_ref-100">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFTung" class="citation news cs1">Tung, Liam. <a rel="nofollow" class="external text" href="https://www.zdnet.com/article/windows-meltdown-spectre-patches-if-you-havent-got-them-blame-your-antivirus/">"Windows Meltdown-Spectre patches: If you haven't got them, blame your antivirus"</a>. ZDNet. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180105103519/https://www.zdnet.com/article/windows-meltdown-spectre-patches-if-you-havent-got-them-blame-your-antivirus/">Archived</a> from the original on 2018-01-05. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=ZDNet&rft.atitle=Windows+Meltdown-Spectre+patches%3A+If+you+haven%27t+got+them%2C+blame+your+antivirus&rft.aulast=Tung&rft.aufirst=Liam&rft_id=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fwindows-meltdown-spectre-patches-if-you-havent-got-them-blame-your-antivirus%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-101"><a href="#cite_ref-101">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.microsoft.com/en-us/help/4072699/important-information-regarding-the-windows-security-updates-released">"Important information regarding the Windows security updates released on 3 January 2018 and anti-virus software"</a>. <a href="/wiki/Microsoft" title="Microsoft">Microsoft</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104174051/https://support.microsoft.com/en-us/help/4072699/important-information-regarding-the-windows-security-updates-released">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Important+information+regarding+the+Windows+security+updates+released+on+3+January+2018+and+anti-virus+software&rft.pub=Microsoft&rft_id=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4072699%2Fimportant-information-regarding-the-windows-security-updates-released&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-102"><a href="#cite_ref-102">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.realworldtech.com/westmere/">"Westmere Arrives"</a>. realworldtech.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180105012039/https://www.realworldtech.com/westmere/">Archived</a> from the original on 2018-01-05. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=realworldtech.com&rft.atitle=Westmere+Arrives&rft_id=https%3A%2F%2Fwww.realworldtech.com%2Fwestmere%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-103"><a href="#cite_ref-103">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation magazine cs1"><a rel="nofollow" class="external text" href="https://www.wired.com/story/critical-intel-flaw-breaks-basic-security-for-most-computers/">"A Critical Intel Flaw Breaks Basic Security for Most Computers"</a>. <a href="/wiki/Wired_(magazine)" title="Wired (magazine)">Wired</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180103204011/https://www.wired.com/story/critical-intel-flaw-breaks-basic-security-for-most-computers/">Archived</a> from the original on 2018-01-03. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Wired&rft.atitle=A+Critical+Intel+Flaw+Breaks+Basic+Security+for+Most+Computers&rft_id=https%3A%2F%2Fwww.wired.com%2Fstory%2Fcritical-intel-flaw-breaks-basic-security-for-most-computers%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-104"><a href="#cite_ref-104">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.pcworld.com/article/3245606/security/intel-x86-cpu-kernel-bug-faq-how-it-affects-pc-mac.html">"Intel CPU kernel bug FAQ: Fix for massive security flaw could slow down PCs and Macs"</a>. PCWorld. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104160407/https://www.pcworld.com/article/3245606/security/intel-x86-cpu-kernel-bug-faq-how-it-affects-pc-mac.html">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=PCWorld&rft.atitle=Intel+CPU+kernel+bug+FAQ%3A+Fix+for+massive+security+flaw+could+slow+down+PCs+and+Macs&rft_id=https%3A%2F%2Fwww.pcworld.com%2Farticle%2F3245606%2Fsecurity%2Fintel-x86-cpu-kernel-bug-faq-how-it-affects-pc-mac.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-105"><a href="#cite_ref-105">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.phoronix.com/scan.php?page=article&item=linux-415-x86pti&num=2">"Initial Benchmarks Of The Performance Impact Resulting From Linux's x86 Security Changes"</a>. Phoronix. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180104180012/https://www.phoronix.com/scan.php?page=article&item=linux-415-x86pti&num=2">Archived</a> from the original on 2018-01-04. Retrieved 2018-01-04.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Phoronix&rft.atitle=Initial+Benchmarks+Of+The+Performance+Impact+Resulting+From+Linux%27s+x86+Security+Changes&rft_id=https%3A%2F%2Fwww.phoronix.com%2Fscan.php%3Fpage%3Darticle%26item%3Dlinux-415-x86pti%26num%3D2&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-PH-20190524-106"><a href="#cite_ref-PH-20190524_106-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFLarabel2019" class="citation news cs1">Larabel, Michael (2019-05-24). <a rel="nofollow" class="external text" href="https://www.phoronix.com/scan.php?page=article&item=sandy-fx-zombieload&num=1">"Benchmarking AMD FX vs. Intel Sandy/Ivy Bridge CPUs Following Spectre, Meltdown, L1TF, Zombieload"</a>. <a href="/wiki/Phoronix" class="mw-redirect" title="Phoronix">Phoronix</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190601164746/https://www.phoronix.com/scan.php?page=article&item=sandy-fx-zombieload&num=1">Archived</a> from the original on 2019-06-01. Retrieved 2019-05-25.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=Phoronix&rft.atitle=Benchmarking+AMD+FX+vs.+Intel+Sandy%2FIvy+Bridge+CPUs+Following+Spectre%2C+Meltdown%2C+L1TF%2C+Zombieload&rft.date=2019-05-24&rft.aulast=Larabel&rft.aufirst=Michael&rft_id=https%3A%2F%2Fwww.phoronix.com%2Fscan.php%3Fpage%3Darticle%26item%3Dsandy-fx-zombieload%26num%3D1&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-PC-20180125-107"><a href="#cite_ref-PC-20180125_107-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFHachman2018" class="citation news cs1">Hachman, Mark (2018-01-25). <a rel="nofollow" class="external text" href="https://www.pcworld.com/article/3251171/components-processors/intels-plan-to-fix-meltdown-in-silicon-raises-more-questions-than-answers.html">"Intel's plan to fix Meltdown in silicon raises more questions than answers – But what silicon?!! Be sure and read the questions Wall Street should have asked"</a>. <a href="/wiki/PC_World" title="PC World">PC World</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180312012223/https://www.pcworld.com/article/3251171/components-processors/intels-plan-to-fix-meltdown-in-silicon-raises-more-questions-than-answers.html">Archived</a> from the original on 2018-03-12. Retrieved 2018-01-26.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=PC+World&rft.atitle=Intel%27s+plan+to+fix+Meltdown+in+silicon+raises+more+questions+than+answers+%E2%80%93+But+what+silicon%3F%21%21+Be+sure+and+read+the+questions+Wall+Street+should+have+asked&rft.date=2018-01-25&rft.aulast=Hachman&rft.aufirst=Mark&rft_id=https%3A%2F%2Fwww.pcworld.com%2Farticle%2F3251171%2Fcomponents-processors%2Fintels-plan-to-fix-meltdown-in-silicon-raises-more-questions-than-answers.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-108"><a href="#cite_ref-108">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite id="CITEREFBright2018" class="citation web cs1">Bright, Peter (2018-04-04). <a rel="nofollow" class="external text" href="https://arstechnica.com/gadgets/2018/04/intel-drops-plans-to-develop-spectre-microcode-for-ancient-chips/">"Intel drops plans to develop Spectre microcode for ancient chips"</a>. ArsTechnica.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20201109025347/https://arstechnica.com/gadgets/2018/04/intel-drops-plans-to-develop-spectre-microcode-for-ancient-chips/">Archived</a> from the original on 2020-11-09. Retrieved 2020-11-03.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=ArsTechnica.com&rft.atitle=Intel+drops+plans+to+develop+Spectre+microcode+for+ancient+chips&rft.date=2018-04-04&rft.aulast=Bright&rft.aufirst=Peter&rft_id=https%3A%2F%2Farstechnica.com%2Fgadgets%2F2018%2F04%2Fintel-drops-plans-to-develop-spectre-microcode-for-ancient-chips%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> <li id="cite_note-109"><a href="#cite_ref-109">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222" /><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/">"Understanding the performance impact of Spectre and Meltdown mitigations on Windows Systems"</a>. Microsoft. 2018-01-09. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20180525200007/https://cloudblogs.microsoft.com/microsoftsecure/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/">Archived</a> from the original on 2018-05-25. Retrieved 2018-01-12.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Understanding+the+performance+impact+of+Spectre+and+Meltdown+mitigations+on+Windows+Systems&rft.pub=Microsoft&rft.date=2018-01-09&rft_id=https%3A%2F%2Fcloudblogs.microsoft.com%2Fmicrosoftsecure%2F2018%2F01%2F09%2Funderstanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AMeltdown+%28security+vulnerability%29" class="Z3988"> </li> </ol></div></div> <div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2>[<a href="/w/index.php?title=Meltdown_(security_vulnerability)&action=edit&section=11" title="Edit section: External links">edit</a>]</div> <ul><li><a rel="nofollow" class="external text" href="https://meltdownattack.com/">Official website of the Meltdown and Spectre vulnerabilities</a></li> <li><a rel="nofollow" class="external text" href="https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html">Google Project Zero write-up</a></li> <li><a rel="nofollow" class="external text" href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754">CVE-2017-5754</a> at <a href="/wiki/National_Vulnerability_Database" title="National Vulnerability Database">National Vulnerability Database</a></li> <li><a rel="nofollow" class="external text" href="https://github.com/IAIK/meltdown">Meltdown's proof-of-concept released by researchers that also published the meltdown paper.</a></li> <li><a rel="nofollow" class="external text" href="https://github.com/raphaelsc/Am-I-affected-by-Meltdown">Am I Affected by Meltdown</a> – Meltdown Checker Tool created by Raphael S. Carvalho</li> <li><a rel="nofollow" class="external text" href="https://www.grc.com/inspectre.htm">Meltdown/Spectre Checker</a> <a href="/wiki/Gibson_Research_Corporation" class="mw-redirect" title="Gibson Research Corporation">Gibson Research Corporation</a></li></ul> <div class="navbox-styles"><style data-mw-deduplicate="TemplateStyles:r1129693374">.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}</style><style data-mw-deduplicate="TemplateStyles:r1236075235">.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}</style></div><div role="navigation" class="navbox" aria-labelledby="Speculative_execution_security_vulnerabilities94" style="padding:3px"><table class="nowraplinks hlist mw-collapsible expanded navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374" /><style data-mw-deduplicate="TemplateStyles:r1239400231">.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}</style><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Speculative_execution_exploits" title="Template:Speculative execution exploits"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Speculative_execution_exploits" title="Template talk:Speculative execution exploits"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Speculative_execution_exploits" title="Special:EditPage/Template:Speculative execution exploits"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Speculative_execution_security_vulnerabilities94" style="font-size:114%;margin:0 4em"><a href="/wiki/Speculative_execution" title="Speculative execution">Speculative execution</a> <a href="/wiki/Vulnerability_(computing)" class="mw-redirect" title="Vulnerability (computing)">security vulnerabilities</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Variants</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Bounds_Check_Bypass" class="mw-redirect" title="Bounds Check Bypass">Bounds Check Bypass (Spectre, Variant 1)</a></li> <li><a href="/wiki/Bounds_Check_Bypass_Store" class="mw-redirect" title="Bounds Check Bypass Store">Bounds Check Bypass Store (Spectre-NG)</a></li> <li><a href="/wiki/Branch_Target_Injection" class="mw-redirect" title="Branch Target Injection">Branch Target Injection (Spectre, Variant 2)</a></li> <li><a href="/wiki/Downfall_(security_vulnerability)" title="Downfall (security vulnerability)">Downfall</a></li> <li><a href="/wiki/Foreshadow" title="Foreshadow">Foreshadow</a></li> <li><a href="/wiki/Lazy_FP_state_restore" title="Lazy FP state restore">Lazy FP state restore (Spectre-NG)</a></li> <li><a href="/wiki/Load_value_injection" title="Load value injection">Load value injection</a></li> <li><a href="/wiki/Microarchitectural_Data_Sampling" title="Microarchitectural Data Sampling">Microarchitectural Data Sampling</a></li> <li><a href="/wiki/Pacman_(security_vulnerability)" title="Pacman (security vulnerability)">Pacman</a></li> <li><a href="/wiki/Retbleed" title="Retbleed">Retbleed</a></li> <li><a href="/wiki/Rogue_Data_Cache_Load" class="mw-redirect" title="Rogue Data Cache Load">Rogue Data Cache Load (Meltdown, Variant 3)</a></li> <li><a href="/wiki/Rogue_System_Register_Read" class="mw-redirect" title="Rogue System Register Read">Rogue System Register Read (Spectre-NG, Variant 3a)</a></li> <li><a href="/wiki/Speculative_Store_Bypass" title="Speculative Store Bypass">Speculative Store Bypass (Spectre-NG, Variant 4)</a></li> <li><a href="/wiki/Spoiler_(security_vulnerability)" title="Spoiler (security vulnerability)">Spoiler</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Topics</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Cache_side-channel_attack" class="mw-redirect" title="Cache side-channel attack">Cache side-channel attack</a></li> <li><a href="/wiki/Hardware_security_bug" title="Hardware security bug">Hardware security bug</a></li> <li><a href="/wiki/Speculative_execution" title="Speculative execution">Speculative execution</a></li> <li><a href="/wiki/Speculative_execution_CPU_vulnerabilities" class="mw-redirect" title="Speculative execution CPU vulnerabilities">Speculative execution CPU vulnerabilities</a></li></ul> </div></td></tr></tbody></table></div> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374" /><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236075235" /></div><div role="navigation" class="navbox" aria-labelledby="Hacking_in_the_2010s789" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374" /><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239400231" /><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Hacking_in_the_2010s" title="Template:Hacking in the 2010s"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Hacking_in_the_2010s" title="Template talk:Hacking in the 2010s"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Hacking_in_the_2010s" title="Special:EditPage/Template:Hacking in the 2010s"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Hacking_in_the_2010s789" style="font-size:114%;margin:0 4em">Hacking in the 2010s</div></th></tr><tr><td class="navbox-abovebelow" colspan="2"><div><table style="width:100%; margin:1px; display:inline-table;"><tbody><tr> <td style="text-align:left; vertical-align:middle; padding:0 0.5em 0 0;" class="noprint">← <a href="/wiki/Template:Hacking_in_the_2000s" title="Template:Hacking in the 2000s">2000s</a></td> <td style="text-align:center; vertical-align:middle;; padding:0 1px;" class=""><a href="/wiki/Timeline_of_computer_security_hacker_history#2010s" class="mw-redirect" title="Timeline of computer security hacker history">Timeline</a></td> <td style="text-align:right; vertical-align:middle;; padding:0 0 0 0.5em;" class="noprint"><a href="/wiki/Template:Hacking_in_the_2020s" title="Template:Hacking in the 2020s">2020s</a> →</td> </tr></tbody></table></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Major incidents</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">2010</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Operation_Aurora" title="Operation Aurora">Operation Aurora</a> (publication of 2009 events)</li> <li><a href="/wiki/February_2010_Australian_cyberattacks" title="February 2010 Australian cyberattacks">Australian cyberattacks</a></li> <li><a href="/wiki/Operation_Olympic_Games" title="Operation Olympic Games">Operation Olympic Games</a></li> <li><a href="/wiki/Shadow_Network" title="Shadow Network">Operation ShadowNet</a></li> <li><a href="/wiki/Operation_Payback" title="Operation Payback">Operation Payback</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2011</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/2011_Canadian_government_hackings" title="2011 Canadian government hackings">Canadian government</a></li> <li><a href="/wiki/DigiNotar" title="DigiNotar">DigiNotar</a></li> <li><a href="/wiki/DNSChanger" title="DNSChanger">DNSChanger</a></li> <li><a href="/wiki/HBGary" title="HBGary">HBGary Federal</a></li> <li><a href="/wiki/Operation_AntiSec" title="Operation AntiSec">Operation AntiSec</a></li> <li><a href="/wiki/2011_PlayStation_Network_outage" title="2011 PlayStation Network outage">PlayStation network outage</a></li> <li><a href="/wiki/RSA_SecurID#March_2011_system_compromise" title="RSA SecurID">RSA SecurID compromise</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2012</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/2012_LinkedIn_hack" title="2012 LinkedIn hack">LinkedIn hack</a></li> <li><a href="/wiki/Stratfor_email_leak" title="Stratfor email leak">Stratfor email leak</a></li> <li><a href="/wiki/Operation_High_Roller" title="Operation High Roller">Operation High Roller</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2013</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/2013_South_Korea_cyberattack" title="2013 South Korea cyberattack">South Korea cyberattack</a></li> <li><a href="/wiki/Snapchat#December_2013_hack" title="Snapchat">Snapchat hack</a></li> <li><a href="/wiki/June_25_cyber_terror" class="mw-redirect" title="June 25 cyber terror">Cyberterrorism attack of June 25</a></li> <li><a href="/wiki/Yahoo_data_breaches#August_2013:_breach" title="Yahoo data breaches">2013 Yahoo! data breach</a></li> <li><a href="/wiki/2013_Singapore_cyberattacks" title="2013 Singapore cyberattacks">Singapore cyberattacks</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2014</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Anthem_medical_data_breach" title="Anthem medical data breach">Anthem medical data breach</a></li> <li><a href="/wiki/Operation_Tovar" title="Operation Tovar">Operation Tovar</a></li> <li><a href="/wiki/2014_celebrity_nude_photo_leak" title="2014 celebrity nude photo leak">2014 celebrity nude photo leak</a></li> <li><a href="/wiki/2014_JPMorgan_Chase_data_breach" title="2014 JPMorgan Chase data breach">2014 JPMorgan Chase data breach</a></li> <li><a href="/wiki/2014_Sony_Pictures_hack" title="2014 Sony Pictures hack">2014 Sony Pictures hack</a></li> <li><a href="/wiki/2014_Russian_hacker_password_theft" title="2014 Russian hacker password theft">Russian hacker password theft</a></li> <li><a href="/wiki/Yahoo_data_breaches#Late_2014:_breach" title="Yahoo data breaches">2014 Yahoo! data breach</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2015</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Office_of_Personnel_Management_data_breach" title="Office of Personnel Management data breach">Office of Personnel Management data breach</a></li> <li><a href="/wiki/HackingTeam#2015_data_breach" title="HackingTeam">HackingTeam</a></li> <li><a href="/wiki/Ashley_Madison_data_breach" title="Ashley Madison data breach">Ashley Madison data breach</a></li> <li><a href="/wiki/VTech#2015_data_breach" title="VTech">VTech data breach</a></li> <li><a href="/wiki/2015_Ukraine_power_grid_hack" title="2015 Ukraine power grid hack">Ukrainian Power Grid Cyberattack</a></li> <li><a href="/wiki/2015%E2%80%932016_SWIFT_banking_hack" title="2015–2016 SWIFT banking hack">SWIFT banking hack</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2016</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Bangladesh_Bank_robbery" title="Bangladesh Bank robbery">Bangladesh Bank robbery</a></li> <li><a href="/wiki/Hollywood_Presbyterian_Medical_Center#Ransomware" title="Hollywood Presbyterian Medical Center">Hollywood Presbyterian Medical Center ransomware incident</a></li> <li><a href="/wiki/Commission_on_Elections_data_breach" title="Commission on Elections data breach">Commission on Elections data breach</a></li> <li><a href="/wiki/Democratic_National_Committee_cyber_attacks" title="Democratic National Committee cyber attacks">Democratic National Committee cyber attacks</a></li> <li><a href="/wiki/Vietnamese_airports_hackings" title="Vietnamese airports hackings">Vietnam Airport Hacks</a></li> <li><a href="/wiki/Democratic_Congressional_Campaign_Committee_cyber_attacks" title="Democratic Congressional Campaign Committee cyber attacks">DCCC cyber attacks</a></li> <li><a href="/wiki/2016_Indian_bank_data_breach" title="2016 Indian bank data breach">Indian Bank data breaches</a></li> <li><a href="/wiki/Surkov_leaks" title="Surkov leaks">Surkov leaks</a></li> <li><a href="/wiki/DDoS_attacks_on_Dyn" title="DDoS attacks on Dyn">Dyn cyberattack</a></li> <li><a href="/wiki/Russian_interference_in_the_2016_United_States_elections" title="Russian interference in the 2016 United States elections">Russian interference in the 2016 U.S. elections</a></li> <li><a href="/wiki/2016_Bitfinex_hack" title="2016 Bitfinex hack">2016 Bitfinex hack</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2017</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/SHA-1#SHAttered_–_first_public_collision" title="SHA-1">SHAttered</a></li> <li><a href="/wiki/2017_Macron_e-mail_leaks" title="2017 Macron e-mail leaks">2017 Macron e-mail leaks</a></li> <li><a href="/wiki/WannaCry_ransomware_attack" title="WannaCry ransomware attack">WannaCry ransomware attack</a></li> <li><a href="/wiki/2017_Westminster_data_breach" title="2017 Westminster data breach">Westminster data breach</a></li> <li><a href="/wiki/Petya_(malware_family)" title="Petya (malware family)">Petya and NotPetya</a> <ul><li><a href="/wiki/2017_Ukraine_ransomware_attacks" title="2017 Ukraine ransomware attacks">2017 Ukraine ransomware attacks</a></li></ul></li> <li><a href="/wiki/2017_Equifax_data_breach" title="2017 Equifax data breach">Equifax data breach</a></li> <li><a href="/wiki/Deloitte#E-mail_hack" title="Deloitte">Deloitte breach</a></li> <li><a href="/wiki/Disqus#October_2017_security_breach" title="Disqus">Disqus breach</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2018</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Trustico#DigiCert_and_Trustico_spat,_2018" title="Trustico">Trustico</a></li> <li><a href="/wiki/Atlanta_government_ransomware_attack" title="Atlanta government ransomware attack">Atlanta cyberattack</a></li> <li><a href="/wiki/2018_SingHealth_data_breach" title="2018 SingHealth data breach">SingHealth data breach</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2019</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/2019_cyberattacks_on_Sri_Lanka" title="2019 cyberattacks on Sri Lanka">Sri Lanka cyberattack</a></li> <li><a href="/wiki/2019_Baltimore_ransomware_attack" title="2019 Baltimore ransomware attack">Baltimore ransomware attack</a></li> <li><a href="/wiki/2019_Bulgarian_Revenue_Agency_hack" title="2019 Bulgarian Revenue Agency hack">Bulgarian revenue agency hack</a></li> <li><a href="/wiki/WhatsApp_snooping_scandal" title="WhatsApp snooping scandal">WhatsApp snooping scandal</a></li> <li><a href="/wiki/Jeff_Bezos_phone_hacking_incident" title="Jeff Bezos phone hacking incident">Jeff Bezos phone hacking incident</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Hacktivism" title="Hacktivism">Hacktivism</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Anonymous_(hacker_group)" title="Anonymous (hacker group)">Anonymous</a> <ul><li><a href="/wiki/Timeline_of_events_associated_with_Anonymous" title="Timeline of events associated with Anonymous">associated events</a></li></ul></li> <li><a href="/wiki/CyberBerkut" title="CyberBerkut">CyberBerkut</a></li> <li><a href="/wiki/Gay_Nigger_Association_of_America" title="Gay Nigger Association of America">GNAA</a></li> <li><a href="/wiki/Goatse_Security" title="Goatse Security">Goatse Security</a></li> <li><a href="/wiki/Lizard_Squad" title="Lizard Squad">Lizard Squad</a></li> <li><a href="/wiki/LulzRaft" title="LulzRaft">LulzRaft</a></li> <li><a href="/wiki/LulzSec" title="LulzSec">LulzSec</a></li> <li><a href="/wiki/DDoS_attacks_on_Dyn#PerpetratorsNew_World_Hackers" title="DDoS attacks on Dyn">DDoS attacks on Dyn#PerpetratorsNew World Hackers</a></li> <li><a href="/wiki/NullCrew" title="NullCrew">NullCrew</a></li> <li><a href="/wiki/OurMine" title="OurMine">OurMine</a></li> <li><a href="/wiki/PayPal_14" title="PayPal 14">PayPal 14</a></li> <li><a href="/wiki/RedHack" title="RedHack">RedHack</a></li> <li><a href="/wiki/Teamp0ison" title="Teamp0ison">Teamp0ison</a></li> <li><a href="/wiki/The_Dark_Overlord_(hacker_group)" title="The Dark Overlord (hacker group)">TDO</a></li> <li><a href="/wiki/UGNazi" title="UGNazi">UGNazi</a></li> <li><a href="/wiki/Ukrainian_Cyber_Alliance" title="Ukrainian Cyber Alliance">Ukrainian Cyber Alliance</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Advanced_persistent_threat" title="Advanced persistent threat">Advanced persistent threats</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Bangladesh_Black_Hat_Hackers" title="Bangladesh Black Hat Hackers">Bangladesh Black Hat Hackers</a></li> <li><a href="/wiki/Bureau_121" title="Bureau 121">Bureau 121</a></li> <li><a href="/wiki/Charming_Kitten" title="Charming Kitten">Charming Kitten</a></li> <li><a href="/wiki/Cozy_Bear" title="Cozy Bear">Cozy Bear</a></li> <li><a href="/wiki/Dark_Basin" title="Dark Basin">Dark Basin</a></li> <li><a href="/wiki/DarkMatter_Group" title="DarkMatter Group">DarkMatter</a></li> <li><a href="/wiki/Elfin_Team" title="Elfin Team">Elfin Team</a></li> <li><a href="/wiki/Equation_Group" title="Equation Group">Equation Group</a></li> <li><a href="/wiki/Fancy_Bear" title="Fancy Bear">Fancy Bear</a></li> <li><a href="/wiki/Stuxnet#History" title="Stuxnet">GOSSIPGIRL</a> (confederation)</li> <li><a href="/wiki/Guccifer_2.0" title="Guccifer 2.0">Guccifer 2.0</a></li> <li><a href="/wiki/HackingTeam" title="HackingTeam">Hacking Team</a></li> <li><a href="/wiki/Helix_Kitten" title="Helix Kitten">Helix Kitten</a></li> <li><a href="/wiki/Iranian_Cyber_Army" title="Iranian Cyber Army">Iranian Cyber Army</a></li> <li><a href="/wiki/Lazarus_Group" title="Lazarus Group">Lazarus Group</a> <ul><li><a href="/wiki/Lazarus_Group#BlueNorOff" title="Lazarus Group">BlueNorOff</a></li> <li><a href="/wiki/Lazarus_Group#AndAriel" title="Lazarus Group">AndAriel</a></li></ul></li> <li><a href="/wiki/NSO_Group" title="NSO Group">NSO Group</a></li> <li><a href="/wiki/Numbered_Panda" title="Numbered Panda">Numbered Panda</a></li> <li><a href="/wiki/PLA_Unit_61398" title="PLA Unit 61398">PLA Unit 61398</a></li> <li><a href="/wiki/PLA_Unit_61486" title="PLA Unit 61486">PLA Unit 61486</a></li> <li><a href="/wiki/PLATINUM_(cybercrime_group)" title="PLATINUM (cybercrime group)">PLATINUM</a></li> <li><a href="/wiki/Pranknet" title="Pranknet">Pranknet</a></li> <li><a href="/wiki/Red_Apollo" title="Red Apollo">Red Apollo</a></li> <li><a href="/wiki/Rocket_Kitten" title="Rocket Kitten">Rocket Kitten</a></li> <li><a href="/wiki/Stealth_Falcon" title="Stealth Falcon">Stealth Falcon</a></li> <li><a href="/wiki/Syrian_Electronic_Army" title="Syrian Electronic Army">Syrian Electronic Army</a></li> <li><a href="/wiki/Tailored_Access_Operations" title="Tailored Access Operations">Tailored Access Operations</a></li> <li><a href="/wiki/The_Shadow_Brokers" title="The Shadow Brokers">The Shadow Brokers</a></li> <li><a href="/wiki/XDedic" title="XDedic">xDedic</a></li> <li><a href="/wiki/Yemen_Cyber_Army" title="Yemen Cyber Army">Yemen Cyber Army</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Hacker" title="Hacker">Individuals</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Ryan_Ackroyd" title="Ryan Ackroyd">Ryan Ackroyd</a></li> <li><a href="/wiki/Mustafa_Al-Bassam" title="Mustafa Al-Bassam">Mustafa Al-Bassam</a></li> <li><a href="/wiki/George_Hotz" title="George Hotz">George Hotz</a></li> <li><a href="/wiki/Guccifer" title="Guccifer">Guccifer</a></li> <li><a href="/wiki/Elliott_Gunton" title="Elliott Gunton">Elliott Gunton</a></li> <li><a href="/wiki/Jeremy_Hammond" title="Jeremy Hammond">Jeremy Hammond</a></li> <li><a href="/wiki/Junaid_Hussain" title="Junaid Hussain">Junaid Hussain</a></li> <li><a href="/wiki/MLT_(hacktivist)" title="MLT (hacktivist)">MLT</a></li> <li><a href="/wiki/Hector_Monsegur" title="Hector Monsegur">Sabu</a></li> <li><a href="/wiki/Roman_Seleznev" title="Roman Seleznev">Track2</a></li> <li><a href="/wiki/Topiary_(hacktivist)" title="Topiary (hacktivist)">Topiary</a></li> <li><a href="/wiki/The_Jester_(hacktivist)" title="The Jester (hacktivist)">The Jester</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Major <a href="/wiki/Vulnerability_(computer_security)" title="Vulnerability (computer security)">vulnerabilities</a> publicly <a href="/wiki/Full_disclosure_(computer_security)" title="Full disclosure (computer security)">disclosed</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Evercookie" title="Evercookie">Evercookie</a> (2010)</li> <li><a href="/wiki/ISeeYou" title="ISeeYou">iSeeYou</a> (2013)</li> <li><a href="/wiki/Heartbleed" title="Heartbleed"> Heartbleed</a> (2014)</li> <li><a href="/wiki/Shellshock_(software_bug)" title="Shellshock (software bug)">Shellshock</a> (2014)</li> <li><a href="/wiki/POODLE" title="POODLE">POODLE</a> (2014)</li> <li><a href="/wiki/Rootpipe" title="Rootpipe">Rootpipe</a> (2014)</li> <li><a href="/wiki/Row_hammer" title="Row hammer">Row hammer</a> (2014)</li> <li><a href="/wiki/Signalling_System_No._7#Protocol_security_vulnerabilities" title="Signalling System No. 7">SS7 vulnerabilities</a> (2014)</li> <li><a href="/wiki/WinShock" title="WinShock">WinShock</a> (2014)</li> <li><a href="/wiki/JASBUG" title="JASBUG">JASBUG</a> (2015)</li> <li><a href="/wiki/Stagefright_(bug)" title="Stagefright (bug)">Stagefright</a> (2015)</li> <li><a href="/wiki/DROWN_attack" title="DROWN attack">DROWN</a> (2016)</li> <li><a href="/wiki/Badlock" title="Badlock">Badlock</a> (2016)</li> <li><a href="/wiki/Dirty_COW" title="Dirty COW">Dirty COW</a> (2016)</li> <li><a href="/wiki/Cloudbleed" title="Cloudbleed">Cloudbleed</a> (2017)</li> <li><a href="/wiki/Broadcom_Corporation#soc-wifi-vulns" title="Broadcom Corporation">Broadcom Wi-Fi</a> (2017)</li> <li><a href="/wiki/EternalBlue" title="EternalBlue">EternalBlue</a> (2017)</li> <li><a href="/wiki/DoublePulsar" title="DoublePulsar">DoublePulsar</a> (2017)</li> <li><a href="/wiki/Intel_Active_Management_Technology#Silent_Bob_is_Silent" title="Intel Active Management Technology">Silent Bob is Silent</a> (2017)</li> <li><a href="/wiki/KRACK" title="KRACK">KRACK</a> (2017)</li> <li><a href="/wiki/ROCA_vulnerability" title="ROCA vulnerability">ROCA vulnerability</a> (2017)</li> <li><a href="/wiki/BlueBorne_(security_vulnerability)" title="BlueBorne (security vulnerability)">BlueBorne</a> (2017)</li> <li><a class="mw-selflink selflink">Meltdown</a> (2018)</li> <li><a href="/wiki/Spectre_(security_vulnerability)" title="Spectre (security vulnerability)">Spectre</a> (2018)</li> <li><a href="/wiki/EFAIL" title="EFAIL">EFAIL</a> (2018)</li> <li><a href="/wiki/Exactis" title="Exactis">Exactis</a> (2018)</li> <li><a href="/wiki/Speculative_Store_Bypass" title="Speculative Store Bypass">Speculative Store Bypass</a> (2018)</li> <li><a href="/wiki/Lazy_FP_state_restore" title="Lazy FP state restore">Lazy FP state restore</a> (2018)</li> <li><a href="/wiki/TLBleed" title="TLBleed">TLBleed</a> (2018)</li> <li><a href="/wiki/SigSpoof" title="SigSpoof">SigSpoof</a> (2018)</li> <li><a href="/wiki/Foreshadow" title="Foreshadow">Foreshadow</a> (2018)</li> <li><a href="/wiki/Wi-Fi_Protected_Access#Dragonblood_attack" title="Wi-Fi Protected Access">Dragonblood</a> (2019)</li> <li><a href="/wiki/Microarchitectural_Data_Sampling" title="Microarchitectural Data Sampling">Microarchitectural Data Sampling</a> (2019)</li> <li><a href="/wiki/BlueKeep" title="BlueKeep">BlueKeep</a> (2019)</li> <li><a href="/wiki/Kr00k" title="Kr00k">Kr00k</a> (2019)</li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Malware" title="Malware">Malware</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">2010</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Ransomware#Bad_Rabbit" title="Ransomware">Bad Rabbit</a></li> <li><a href="/wiki/BlackEnergy#BlackEnergy_2_(BE2)" title="BlackEnergy"> Black Energy 2</a></li> <li><a href="/wiki/SpyEye" title="SpyEye">SpyEye</a></li> <li><a href="/wiki/Stuxnet" title="Stuxnet">Stuxnet</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2011</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Coreflood" title="Coreflood">Coreflood</a></li> <li><a href="/wiki/Alureon" title="Alureon">Alureon</a></li> <li><a href="/wiki/Duqu" title="Duqu">Duqu</a></li> <li><a href="/wiki/Kelihos_botnet" title="Kelihos botnet">Kelihos</a></li> <li><a href="/wiki/Metulji_botnet" title="Metulji botnet">Metulji botnet</a></li> <li><a href="/wiki/Stars_virus" title="Stars virus">Stars</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2012</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Carna_botnet" title="Carna botnet">Carna</a></li> <li><a href="/wiki/Dexter_(malware)" title="Dexter (malware)">Dexter</a></li> <li><a href="/wiki/FBI_MoneyPak_Ransomware" title="FBI MoneyPak Ransomware">FBI</a></li> <li><a href="/wiki/Flame_(malware)" title="Flame (malware)">Flame</a></li> <li><a href="/wiki/Mahdi_(malware)" title="Mahdi (malware)">Mahdi</a></li> <li><a href="/wiki/Red_October_(malware)" title="Red October (malware)">Red October</a></li> <li><a href="/wiki/Shamoon" title="Shamoon">Shamoon</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2013</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/CryptoLocker" title="CryptoLocker">CryptoLocker</a></li> <li><a href="/wiki/2013_South_Korea_cyberattack" title="2013 South Korea cyberattack">DarkSeoul</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2014</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Brambul" title="Brambul">Brambul</a></li> <li><a href="/wiki/BlackEnergy#BlackEnergy_3_(BE3)" title="BlackEnergy"> Black Energy 3</a></li> <li><a href="/wiki/Carbanak" title="Carbanak">Carbanak</a></li> <li><a href="/wiki/Careto_(malware)" title="Careto (malware)">Careto</a></li> <li><a href="/wiki/DarkHotel" title="DarkHotel">DarkHotel</a></li> <li><a href="/wiki/Duqu_2.0" title="Duqu 2.0">Duqu 2.0</a></li> <li><a href="/wiki/FinFisher" title="FinFisher">FinFisher</a></li> <li><a href="/wiki/Gameover_ZeuS" title="Gameover ZeuS">Gameover ZeuS</a></li> <li><a href="/wiki/Regin_(malware)" title="Regin (malware)">Regin</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2015</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Dridex" title="Dridex">Dridex</a></li> <li><a href="/wiki/Hidden_Tear" title="Hidden Tear">Hidden Tear</a></li> <li><a href="/wiki/Rombertik" title="Rombertik">Rombertik</a></li> <li><a href="/wiki/TeslaCrypt" title="TeslaCrypt">TeslaCrypt</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2016</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Hitler-Ransomware" title="Hitler-Ransomware">Hitler</a></li> <li><a href="/wiki/Jigsaw_(ransomware)" title="Jigsaw (ransomware)">Jigsaw</a></li> <li><a href="/wiki/KeRanger" title="KeRanger">KeRanger</a></li> <li><a href="/wiki/Necurs_botnet" title="Necurs botnet">Necurs</a></li> <li><a href="/wiki/MEMZ" title="MEMZ">MEMZ</a></li> <li><a href="/wiki/Mirai_(malware)" title="Mirai (malware)">Mirai</a></li> <li><a href="/wiki/Pegasus_(spyware)" title="Pegasus (spyware)">Pegasus</a></li> <li><a href="/wiki/Petya_(malware_family)" title="Petya (malware family)">Petya and NotPetya</a></li> <li><a href="/wiki/X-Agent" title="X-Agent">X-Agent</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2017</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/BrickerBot" title="BrickerBot">BrickerBot</a></li> <li><a href="/wiki/Kirk_Ransomware" title="Kirk Ransomware">Kirk</a></li> <li><a href="/wiki/LogicLocker" title="LogicLocker">LogicLocker</a></li> <li><a href="/wiki/Rensenware" title="Rensenware">Rensenware</a></li> <li><a href="/wiki/Triton_(malware)" title="Triton (malware)">Triton</a></li> <li><a href="/wiki/WannaCry_ransomware_attack" title="WannaCry ransomware attack">WannaCry</a></li> <li><a href="/wiki/Xafecopy_Trojan" title="Xafecopy Trojan">XafeCopy</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2018</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/VPNFilter" title="VPNFilter">VPNFilter</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">2019</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Grum_botnet" title="Grum botnet">Grum</a></li> <li><a href="/wiki/Joanap" title="Joanap">Joanap</a></li> <li><a href="/wiki/NetTraveler" title="NetTraveler">NetTraveler</a></li> <li><a href="/wiki/Chaos_Computer_Club#Staatstrojaner_affair" title="Chaos Computer Club">R2D2</a></li> <li><a href="/wiki/Tiny_Banker_Trojan" title="Tiny Banker Trojan">Tinba</a></li> <li><a href="/wiki/Titanium_(malware)" title="Titanium (malware)">Titanium</a></li> <li><a href="/wiki/ZeroAccess_botnet" title="ZeroAccess botnet">ZeroAccess botnet</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr></tbody></table></div> <style data-mw-deduplicate="TemplateStyles:r1130092004">.mw-parser-output .portal-bar{font-size:88%;font-weight:bold;display:flex;justify-content:center;align-items:baseline}.mw-parser-output .portal-bar-bordered{padding:0 2em;background-color:#fdfdfd;border:1px solid #a2a9b1;clear:both;margin:1em auto 0}.mw-parser-output .portal-bar-related{font-size:100%;justify-content:flex-start}.mw-parser-output .portal-bar-unbordered{padding:0 1.7em;margin-left:0}.mw-parser-output .portal-bar-header{margin:0 1em 0 0.5em;flex:0 0 auto;min-height:24px}.mw-parser-output .portal-bar-content{display:flex;flex-flow:row wrap;flex:0 1 auto;padding:0.15em 0;column-gap:1em;align-items:baseline;margin:0;list-style:none}.mw-parser-output .portal-bar-content-related{margin:0;list-style:none}.mw-parser-output .portal-bar-item{display:inline-block;margin:0.15em 0.2em;min-height:24px;line-height:24px}@media screen and (max-width:768px){.mw-parser-output .portal-bar{font-size:88%;font-weight:bold;display:flex;flex-flow:column wrap;align-items:baseline}.mw-parser-output .portal-bar-header{text-align:center;flex:0;padding-left:0.5em;margin:0 auto}.mw-parser-output .portal-bar-related{font-size:100%;align-items:flex-start}.mw-parser-output .portal-bar-content{display:flex;flex-flow:row wrap;align-items:center;flex:0;column-gap:1em;border-top:1px solid #a2a9b1;margin:0 auto;list-style:none}.mw-parser-output .portal-bar-content-related{border-top:none;margin:0;list-style:none}}.mw-parser-output .navbox+link+.portal-bar,.mw-parser-output .navbox+style+.portal-bar,.mw-parser-output .navbox+link+.portal-bar-bordered,.mw-parser-output .navbox+style+.portal-bar-bordered,.mw-parser-output .sister-bar+link+.portal-bar,.mw-parser-output .sister-bar+style+.portal-bar,.mw-parser-output .portal-bar+.navbox-styles+.navbox,.mw-parser-output .portal-bar+.navbox-styles+.sister-bar{margin-top:-1px}</style><div class="portal-bar noprint metadata noviewer portal-bar-bordered" role="navigation" aria-label="Portals"><a href="/wiki/Wikipedia:Contents/Portals" title="Wikipedia:Contents/Portals">Portal</a>:<ul class="portal-bar-content"><li class="portal-bar-item"><a href="/wiki/File:Emblem-money.svg" class="mw-file-description"><img alt="icon" src="//upload.wikimedia.org/wikipedia/commons/thumb/f/f3/Emblem-money.svg/20px-Emblem-money.svg.png" decoding="async" width="19" height="19" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/f/f3/Emblem-money.svg/40px-Emblem-money.svg.png 1.5x" data-file-width="48" data-file-height="48" /></a> <a href="/wiki/Portal:Business_and_economics" class="mw-redirect" title="Portal:Business and economics">Business and economics</a></li></ul></div>    </div><noscript><img src="https://login.wikimedia.org/wiki/Special:CentralAutoLogin/start?useformat=desktop&type=1x1&usesul3=0" alt="" width="1" height="1" style="border: none; position: absolute;"></noscript> <div class="printfooter" data-nosnippet="">Retrieved from "<a dir="ltr" href="https://en.wikipedia.org/w/index.php?title=Meltdown_(security_vulnerability)&oldid=1265360095">https://en.wikipedia.org/w/index.php?title=Meltdown_(security_vulnerability)&oldid=1265360095</a>"</div></div> <div id="catlinks" class="catlinks" data-mw="interface"><div id="mw-normal-catlinks" class="mw-normal-catlinks"><a href="/wiki/Help:Category" title="Help:Category">Categories</a>: <ul><li><a href="/wiki/Category:Intel_x86_microprocessors" title="Category:Intel x86 microprocessors">Intel x86 microprocessors</a></li><li><a href="/wiki/Category:Transient_execution_CPU_vulnerabilities" title="Category:Transient execution CPU vulnerabilities">Transient execution CPU vulnerabilities</a></li><li><a href="/wiki/Category:X86_memory_management" title="Category:X86 memory management">X86 memory management</a></li><li><a href="/wiki/Category:2018_in_computing" title="Category:2018 in computing">2018 in computing</a></li></ul></div><div id="mw-hidden-catlinks" class="mw-hidden-catlinks mw-hidden-cats-hidden">Hidden categories: <ul><li><a href="/wiki/Category:Articles_with_short_description" title="Category:Articles with short description">Articles with short description</a></li><li><a href="/wiki/Category:Short_description_is_different_from_Wikidata" title="Category:Short description is different from Wikidata">Short description is different from Wikidata</a></li><li><a href="/wiki/Category:Use_dmy_dates_from_June_2019" title="Category:Use dmy dates from June 2019">Use dmy dates from June 2019</a></li><li><a href="/wiki/Category:All_articles_with_unsourced_statements" title="Category:All articles with unsourced statements">All articles with unsourced statements</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_November_2020" title="Category:Articles with unsourced statements from November 2020">Articles with unsourced statements from November 2020</a></li><li><a href="/wiki/Category:Articles_needing_cleanup_from_January_2018" title="Category:Articles needing cleanup from January 2018">Articles needing cleanup from January 2018</a></li><li><a href="/wiki/Category:All_pages_needing_cleanup" title="Category:All pages needing cleanup">All pages needing cleanup</a></li><li><a href="/wiki/Category:Articles_with_sections_that_need_to_be_turned_into_prose_from_January_2018" title="Category:Articles with sections that need to be turned into prose from January 2018">Articles with sections that need to be turned into prose from January 2018</a></li><li><a href="/wiki/Category:All_articles_lacking_reliable_references" title="Category:All articles lacking reliable references">All articles lacking reliable references</a></li><li><a href="/wiki/Category:Articles_lacking_reliable_references_from_January_2018" title="Category:Articles lacking reliable references from January 2018">Articles lacking reliable references from January 2018</a></li></ul></div></div> </div> </main> </div> <div class="mw-footer-container"> <footer id="footer" class="mw-footer" > <ul id="footer-info"> <li id="footer-info-lastmod"> This page was last edited on 26 December 2024, at 14:35 (UTC).</li> <li id="footer-info-copyright">Text is available under the <a href="/wiki/Wikipedia:Text_of_the_Creative_Commons_Attribution-ShareAlike_4.0_International_License" title="Wikipedia:Text of the Creative Commons Attribution-ShareAlike 4.0 International License">Creative Commons Attribution-ShareAlike 4.0 License</a>; additional terms may apply. By using this site, you agree to the <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use" class="extiw" title="foundation:Special:MyLanguage/Policy:Terms of Use">Terms of Use</a> and <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy" class="extiw" title="foundation:Special:MyLanguage/Policy:Privacy policy">Privacy Policy</a>. Wikipedia® is a registered trademark of the <a rel="nofollow" class="external text" href="https://wikimediafoundation.org/">Wikimedia Foundation, Inc.</a>, a non-profit organization.</li> </ul> <ul id="footer-places"> <li id="footer-places-privacy"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy">Privacy policy</a></li> <li id="footer-places-about"><a href="/wiki/Wikipedia:About">About Wikipedia</a></li> <li id="footer-places-disclaimers"><a href="/wiki/Wikipedia:General_disclaimer">Disclaimers</a></li> <li id="footer-places-contact"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us">Contact Wikipedia</a></li> <li id="footer-places-wm-codeofconduct"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Universal_Code_of_Conduct">Code of Conduct</a></li> <li id="footer-places-developers"><a href="https://developer.wikimedia.org">Developers</a></li> <li id="footer-places-statslink"><a href="https://stats.wikimedia.org/#/en.wikipedia.org">Statistics</a></li> <li id="footer-places-cookiestatement"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Cookie_statement">Cookie statement</a></li> <li id="footer-places-mobileview"><a href="//en.m.wikipedia.org/w/index.php?title=Meltdown_(security_vulnerability)&mobileaction=toggle_view_mobile" class="noprint stopMobileRedirectToggle">Mobile view</a></li> </ul> <ul id="footer-icons" class="noprint"> <li id="footer-copyrightico"><a href="https://www.wikimedia.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><picture><source media="(min-width: 500px)" srcset="/static/images/footer/wikimedia-button.svg" width="84" height="29"><img src="/static/images/footer/wikimedia.svg" width="25" height="25" alt="Wikimedia Foundation" lang="en" loading="lazy"></picture></a></li> <li id="footer-poweredbyico"><a href="https://www.mediawiki.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><picture><source media="(min-width: 500px)" srcset="/w/resources/assets/poweredby_mediawiki.svg" width="88" height="31"><img src="/w/resources/assets/mediawiki_compact.svg" alt="Powered by MediaWiki" lang="en" width="25" height="25" loading="lazy"></picture></a></li> </ul> </footer> </div> </div> </div> <div class="vector-header-container vector-sticky-header-container"> <div id="vector-sticky-header" class="vector-sticky-header"> <div class="vector-sticky-header-start"> <div class="vector-sticky-header-icon-start vector-button-flush-left vector-button-flush-right" aria-hidden="true"> <button class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-sticky-header-search-toggle" tabindex="-1" data-event-name="ui.vector-sticky-search-form.icon"> Search </button> </div> <div role="search" class="vector-search-box-vue vector-search-box-show-thumbnail vector-search-box"> <div class="vector-typeahead-search-container"> <div class="cdx-typeahead-search cdx-typeahead-search--show-thumbnail"> <form action="/w/index.php" id="vector-sticky-search-form" class="cdx-search-input cdx-search-input--has-end-button"> <div class="cdx-search-input__input-wrapper" data-search-loc="header-moved"> <div class="cdx-text-input cdx-text-input--has-start-icon"> <input class="cdx-text-input__input" type="search" name="search" placeholder="Search Wikipedia"> </div> <input type="hidden" name="title" value="Special:Search"> </div> <button class="cdx-button cdx-search-input__end-button">Search</button> </form> </div> </div> </div> <div class="vector-sticky-header-context-bar"> <nav aria-label="Contents" class="vector-toc-landmark"> <div id="vector-sticky-header-toc" class="vector-dropdown mw-portlet mw-portlet-sticky-header-toc vector-sticky-header-toc vector-button-flush-left" > <input type="checkbox" id="vector-sticky-header-toc-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-sticky-header-toc" class="vector-dropdown-checkbox " aria-label="Toggle the table of contents" > <label id="vector-sticky-header-toc-label" for="vector-sticky-header-toc-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Toggle the table of contents </label> <div class="vector-dropdown-content"> <div id="vector-sticky-header-toc-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <div class="vector-sticky-header-context-bar-primary" aria-hidden="true" >Meltdown (security vulnerability)</div> </div> </div> <div class="vector-sticky-header-end" aria-hidden="true"> <div class="vector-sticky-header-icons"> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-talk-sticky-header" tabindex="-1" data-event-name="talk-sticky-header"> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-subject-sticky-header" tabindex="-1" data-event-name="subject-sticky-header"> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-history-sticky-header" tabindex="-1" data-event-name="history-sticky-header"> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only mw-watchlink" id="ca-watchstar-sticky-header" tabindex="-1" data-event-name="watch-sticky-header"> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-edit-sticky-header" tabindex="-1" data-event-name="wikitext-edit-sticky-header"> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-ve-edit-sticky-header" tabindex="-1" data-event-name="ve-edit-sticky-header"> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-viewsource-sticky-header" tabindex="-1" data-event-name="ve-edit-protected-sticky-header"> </a> </div> <div class="vector-sticky-header-buttons"> <button class="cdx-button cdx-button--weight-quiet mw-interlanguage-selector" id="p-lang-btn-sticky-header" tabindex="-1" data-event-name="ui.dropdown-p-lang-btn-sticky-header"> 22 languages </button> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--action-progressive" id="ca-addsection-sticky-header" tabindex="-1" data-event-name="addsection-sticky-header"> Add topic </a> </div> <div class="vector-sticky-header-icon-end"> <div class="vector-user-links"> </div> </div> </div> </div> </div> <div class="mw-portlet mw-portlet-dock-bottom emptyPortlet" id="p-dock-bottom"> <ul> </ul> </div> <script>(RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgHostname":"mw-web.codfw.main-5c6f46dcf-llnks","wgBackendResponseTime":187,"wgPageParseReport":{"limitreport":{"cputime":"1.095","walltime":"1.268","ppvisitednodes":{"value":7792,"limit":1000000},"postexpandincludesize":{"value":308294,"limit":2097152},"templateargumentsize":{"value":4544,"limit":2097152},"expansiondepth":{"value":18,"limit":100},"expensivefunctioncount":{"value":10,"limit":500},"unstrip-depth":{"value":1,"limit":20},"unstrip-size":{"value":433124,"limit":5000000},"entityaccesscount":{"value":0,"limit":400},"timingprofile":["100.00% 1070.853 1 -total"," 55.10% 590.013 1 Template:Reflist"," 34.19% 366.096 77 Template:Cite_web"," 11.03% 118.104 26 Template:Cite_news"," 8.40% 89.979 4 Template:Navbox"," 7.89% 84.456 1 Template:Infobox_bug"," 7.49% 80.216 1 Template:Infobox"," 6.91% 74.006 1 Template:Short_description"," 6.62% 70.925 1 Template:Speculative_execution_exploits"," 4.62% 49.455 3 Template:Citation_needed"]},"scribunto":{"limitreport-timeusage":{"value":"0.688","limit":"10.000"},"limitreport-memusage":{"value":7382737,"limit":52428800}},"cachereport":{"origin":"mw-web.codfw.main-5c6f46dcf-lkrmk","timestamp":"20250331042620","ttl":70426,"transientcontent":true}}});});</script> <script type="application/ld+json">{"@context":"https:\/\/schema.org","@type":"Article","name":"Meltdown (security vulnerability)","url":"https:\/\/en.wikipedia.org\/wiki\/Meltdown_(security_vulnerability)","sameAs":"http:\/\/www.wikidata.org\/entity\/Q47036859","mainEntity":"http:\/\/www.wikidata.org\/entity\/Q47036859","author":{"@type":"Organization","name":"Contributors to Wikimedia projects"},"publisher":{"@type":"Organization","name":"Wikimedia Foundation, Inc.","logo":{"@type":"ImageObject","url":"https:\/\/www.wikimedia.org\/static\/images\/wmf-hor-googpub.png"}},"datePublished":"2018-01-03T22:48:53Z","dateModified":"2024-12-26T14:35:32Z","image":"https:\/\/upload.wikimedia.org\/wikipedia\/commons\/8\/86\/Meltdown_logo_with_text.svg","headline":"vulnerability in modern microprocessors which permits unauthorized memory reads"}</script> </body> </html>