{"id":355,"date":"2018-05-09T22:44:33","date_gmt":"2018-05-09T22:44:33","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/"},"modified":"2018-05-09T22:44:33","modified_gmt":"2018-05-09T22:44:33","slug":"every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/","title":{"rendered":"Every major OS maker misread Intel’s docs. Now their kernels can be hijacked or crashed"},"content":{"rendered":"
<\/div>\n

Linux, Windows, macOS, FreeBSD, and some implementations of Xen have a design flaw that could allow attackers to, at best, crash Intel and AMD-powered computers.<\/p>\n

At worst, miscreants can, potentially, “gain access to sensitive memory information or control low-level operating system functions,\u201d which is a fancy way of saying peek at kernel memory, or hijack the critical code running the machine.<\/p>\n

The vulnerabilities can be exploited by malware running on a computer, or a malicious logged-in user. Patches are now available to correct the near-industry-wide programming blunders.<\/p>\n

As detailed by CERT on Tuesday<\/a>, the security cockup, labeled CVE-2018-8897<\/a>, appears to have been caused by developers at Microsoft, Apple, and other organizations misunderstanding the way Intel and AMD processors handle one particular special exception.<\/p>\n

Indeed, CERT noted: “The error appears to be due to developer interpretation of existing documentation.” In other words, programmers misunderstood Intel and AMD’s manuals, which may not have been very clear.<\/p>\n

You’re fired (the interrupt, that is)<\/span><\/h3>\n

Here’s a deep dive put as gently as possible. At the heart of the issue is the POP SS<\/code> instruction, which takes from the running program’s stack a value used to select the stack’s segment, and puts that number into the CPU’s stack selector register. This is all to do with memory segmentation that modern operating systems mostly ignore, and you can, too. The POP SS<\/code> instruction is specially handled by the CPU so that the stack cannot be left in an inconsistent state if an interrupt fires while it is executing.<\/p>\n

An application can set a debug breakpoint for the memory location where that stack selector will be pulled from the stack by POP SS<\/code>. That is, when the app uses POP SS<\/code>, it will generate a special exception when the processor touches a particular part of RAM to fetch the stack selector.<\/p>\n

Now, here’s the clever trick. To exploit this situation, the instruction immediately after the POP SS<\/code> instruction has to be an INT<\/code> instruction, which triggers an interrupt. These software-generated interrupts are sometimes used by user programs to activate the kernel so it can do work for the running process, such as open a file.<\/p>\n

On Intel and AMD machines, the software-generated interrupt instruction immediately after POP SS<\/code> causes the processor to enter the kernel’s interrupt handler. Then the debug exception fires, because POP SS<\/code> caused the exception to be deferred.<\/p>\n

Operating system designers didn’t expect this. They read Intel’s x86-64 manuals, and concluded the handler starts in an uninterruptable state. But now there’s an unexpected debug exception to deal with while very early inside the interrupt handler.<\/p>\n

This confuses the heck out of the kernel, causing it to, in certain circumstances, rely on data controlled by un-privileged user software, as explained by the flaw’s discoverers Nick Peterson of Everdox Tech, and Nemanja Mulasmajic of triplefault.io, in their technical explanation<\/a> (PDF):<\/p>\n

The upshot is that, on Intel boxes, the user application can use POP SS<\/code> and INT<\/code> to exploit the above misunderstanding, and control the special pointer GSBASE<\/code> in the interrupt handler. On AMD, the app can control GSBASE<\/code> and the stack pointer. This can either be used to crash the kernel, by making it touch un-mapped memory, extract parts of protected kernel memory, or tweak its internal structures to knock over the system or joyride its operations.<\/p>\n

Any exploitation attempt is more likely to crash the kernel than cause any serious harm, we reckon. However, like Meltdown<\/a>, as bugs go, it’s a little embarrassing for the industry, and it ought to be patched to be on the safe side.<\/p>\n

Manipulations<\/span><\/h3>\n

The FreeBSD advisory<\/a> on the problem explains it further. \u201cOn x86 architecture systems, the stack is represented by the combination of a stack segment and a stack pointer, which must remain in sync for proper operation,\u201d the OS\u2019s developers wrote. \u201cInstructions related to manipulating the stack segment have special handling to facilitate consistency with changes to the stack pointer.<\/p>\n

\u201cThe MOV SS and POP SS instructions inhibit debug exceptions until the instruction boundary following the next instruction. If that instruction is a system call or similar instruction that transfers control to the operating system, the debug exception will be handled in the kernel context instead of the user context.\u201d<\/p>\n

The result? \u201cAn authenticated local attacker may be able to read sensitive data in kernel memory, control low-level operating system functions, or may panic the system.\u201d<\/p>\n

Exploiting such on Windows, according to Microsoft\u2019s kernel advisory<\/a>, would mean \u201can attacker would first have to log on to the system. An attacker could then run a specially crafted application to take control of an affected system.\u201d<\/p>\n

Which \u2013 gulp! – isn\u2019t a very far-fetched scenario, unless you run a tight ship of no untrusted code.<\/p>\n

Red Hat has patches<\/a> ready to roll, as does Ubuntu<\/a>, and Apple for macOS<\/a>.<\/p>\n

The Linux kernel has also been fixed, way back on March 23, 2018. A patch is already present in versions 4.15.14, 4.14.31, 4.9.91, 4.4.125, plus older 4.1, 3.16, and 3.2 branches.<\/p>\n

Microsoft\u2019s got it sorted, for Windows 7 through 10 and Windows Server 2008 through version 1803. Xen has patches for versions 4.6 through 4.10<\/a>. VMware\u2019s hypervisors aren\u2019t at risk, but vCenter Server has a workaround<\/a> and vSphere Integrated containers await a fix, but both are rated merely \u201cpotentially affected.\u201d<\/p>\n

See the above CERT link for all affected vendors and their responses, and apply updates as necessary.<\/p>\n

All sources are at pains to point out that while this issue derives from an x86-64 instruction, kernel programmers, and not Chipzilla, are to blame. It seems lots of coders have simply misunderstood how to handle debug exceptions, and made similar mistakes over a long period of time.<\/p>\n

\n

#Intel<\/a> released the 67th edition of the Software Developer\u2019s Manuals with interrupt related modifications https:\/\/t.co\/qh7jNcQQFN<\/a> pic.twitter.com\/XZ6nkHrITV<\/a><\/p>\n

\u2014 InstLatX64 (@InstLatX64) May 8, 2018<\/a><\/p><\/blockquote>\n

The Register<\/em> expects plenty of OS developers are about to be sent to compulsory reeducation sessions on the x86-64 architecture, now that Intel has updated its manuals to clarify the handling of stack selector instructions, and that readers get to do the emergency patch thing. Which you should be pretty good at by now. \u00ae<\/p>\n

Sponsored:<\/span> Minds Mastering Machines – Call for papers now open<\/a><\/p>\n

Read More HERE<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Grab those patches while Chipzilla updates its manuals Linux, Windows, macOS, FreeBSD, and some implementations of Xen have a design flaw that could allow attackers to, at best, crash Intel and AMD-powered computers.\u2026 Read More HERE…<\/p>\n","protected":false},"author":1,"featured_media":356,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_layout":"default_layout","footnotes":""},"categories":[63],"tags":[],"class_list":["post-355","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-the-register"],"yoast_head":"\nEvery major OS maker misread Intel's docs. Now their kernels can be hijacked or crashed 2026 | ThreatsHub Cybersecurity News<\/title>\n<meta name=\"description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Every major OS maker misread Intel's docs. Now their kernels can be hijacked or crashed 2026 | ThreatsHub Cybersecurity News\" \/>\n<meta property=\"og:description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/\" \/>\n<meta property=\"og:site_name\" content=\"ThreatsHub Cybersecurity News\" \/>\n<meta property=\"article:published_time\" content=\"2018-05-09T22:44:33+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"794\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"thadmin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@thadmin\" \/>\n<meta name=\"twitter:site\" content=\"@threatshub\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"thadmin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/\"},\"author\":{\"name\":\"thadmin\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/b07e00649871a6dd150cd57b33f7db66\"},\"headline\":\"Every major OS maker misread Intel’s docs. Now their kernels can be hijacked or crashed\",\"datePublished\":\"2018-05-09T22:44:33+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/\"},\"wordCount\":1044,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg\",\"articleSection\":[\"The Register\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/\",\"name\":\"Every major OS maker misread Intel's docs. Now their kernels can be hijacked or crashed 2026 | ThreatsHub Cybersecurity News\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg\",\"datePublished\":\"2018-05-09T22:44:33+00:00\",\"description\":\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/05\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg\",\"width\":1200,\"height\":794},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Every major OS maker misread Intel’s docs. Now their kernels can be hijacked or crashed\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"name\":\"ThreatsHub Cybersecurity News\",\"description\":\"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"alternateName\":\"Threatshub.org\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\",\"name\":\"ThreatsHub.org\",\"alternateName\":\"Threatshub.org\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"width\":432,\"height\":435,\"caption\":\"ThreatsHub.org\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/threatshub\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/b07e00649871a6dd150cd57b33f7db66\",\"name\":\"thadmin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/64b2823a5e0933c780cab004122ddae4375b28e7a87014931eaea97478ab540f?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/64b2823a5e0933c780cab004122ddae4375b28e7a87014931eaea97478ab540f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/64b2823a5e0933c780cab004122ddae4375b28e7a87014931eaea97478ab540f?s=96&d=mm&r=g\",\"caption\":\"thadmin\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/thadmin\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Every major OS maker misread Intel's docs. Now their kernels can be hijacked or crashed 2026 | ThreatsHub Cybersecurity News","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/","og_locale":"en_US","og_type":"article","og_title":"Every major OS maker misread Intel's docs. Now their kernels can be hijacked or crashed 2026 | ThreatsHub Cybersecurity News","og_description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","og_url":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/","og_site_name":"ThreatsHub Cybersecurity News","article_published_time":"2018-05-09T22:44:33+00:00","og_image":[{"width":1200,"height":794,"url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg","type":"image\/jpeg"}],"author":"thadmin","twitter_card":"summary_large_image","twitter_creator":"@thadmin","twitter_site":"@threatshub","twitter_misc":{"Written by":"thadmin","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#article","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/"},"author":{"name":"thadmin","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/b07e00649871a6dd150cd57b33f7db66"},"headline":"Every major OS maker misread Intel’s docs. Now their kernels can be hijacked or crashed","datePublished":"2018-05-09T22:44:33+00:00","mainEntityOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/"},"wordCount":1044,"commentCount":0,"publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#primaryimage"},"thumbnailUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg","articleSection":["The Register"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/","url":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/","name":"Every major OS maker misread Intel's docs. Now their kernels can be hijacked or crashed 2026 | ThreatsHub Cybersecurity News","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#primaryimage"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#primaryimage"},"thumbnailUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg","datePublished":"2018-05-09T22:44:33+00:00","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","breadcrumb":{"@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#primaryimage","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2018\/05\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed.jpg","width":1200,"height":794},{"@type":"BreadcrumbList","@id":"https:\/\/www.threatshub.org\/blog\/every-major-os-maker-misread-intels-docs-now-their-kernels-can-be-hijacked-or-crashed\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.threatshub.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Every major OS maker misread Intel’s docs. Now their kernels can be hijacked or crashed"}]},{"@type":"WebSite","@id":"https:\/\/www.threatshub.org\/blog\/#website","url":"https:\/\/www.threatshub.org\/blog\/","name":"ThreatsHub Cybersecurity News","description":"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform","publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"alternateName":"Threatshub.org","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.threatshub.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.threatshub.org\/blog\/#organization","name":"ThreatsHub.org","alternateName":"Threatshub.org","url":"https:\/\/www.threatshub.org\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","width":432,"height":435,"caption":"ThreatsHub.org"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/threatshub"]},{"@type":"Person","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/b07e00649871a6dd150cd57b33f7db66","name":"thadmin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/64b2823a5e0933c780cab004122ddae4375b28e7a87014931eaea97478ab540f?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/64b2823a5e0933c780cab004122ddae4375b28e7a87014931eaea97478ab540f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/64b2823a5e0933c780cab004122ddae4375b28e7a87014931eaea97478ab540f?s=96&d=mm&r=g","caption":"thadmin"},"sameAs":["https:\/\/x.com\/thadmin"]}]}},"_links":{"self":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/comments?post=355"}],"version-history":[{"count":0,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/355\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media\/356"}],"wp:attachment":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media?parent=355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/categories?post=355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/tags?post=355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}