/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Intel says CPU flaws not limited to its own chips, exploits can't corrupt/modify data but can access sensitive data, is working with AMD and ARM to find fixes

unclear if there's even manufacturing capacity for this— OR customers will have to wait for secure processors to reach the market, and do their own risk analysis as to whether they need to swap out all affected hardware. Thanks: @inafried

Axios Ina Fried

Discussion

  • @nicoleperlroth Nicole Perlroth on x
    11. Chipmakers like Intel will have to do a full recall— unclear if there's even manufacturing capacity for this— OR customers will have to wait for secure processors to reach the market, and do their own risk analysis as to whether they need to swap out all affected hardware.
  • @cloud_opinion Cloud Opinion on x
    Do any self driving cars use Intel chips?
  • @timgostony Tim Gostony on x
    Impact of the patch for the Intel bug on my AWS EC2 instances running Linux, a t1.micro and m3.medium. #KPTI pic.twitter.com/n3uZsZ38iV
  • @internetofs**t Internet of S**t on x
    bugs, ranked Heartbleed: whoops, the internet is burning Shellshock: oh no, bash is broken sorry Meltdown/spectre: we had a nuclear reactor accident twenty years ago and just found it uhhhh yeah good luck
  • @eastdakota Matthew Prince on x
    And if it turns out AMD isn't vulnerable to this bug (and the tech folks around here think think they're likely not) then this press release (on which $AMD fell and $INTC recovered) will come to haunt Intel. #ugly http://newsroom.intel.com/...
  • @nicoleperlroth Nicole Perlroth on x
    4) Spectre is harder to exploit, but has no easy fix, and is far more pervasive. Researchers say it is highly likely the threat from Spectre will be with us for the decade to come.
  • @dguido Dan Guido on x
    If you have an Intel CPU with the “PCID” feature, then the security fix for Spectre/Meltdown will have less performance overhead. On macOS, check if you have PCID by opening a terminal and running: ‘sysctl machdep.cpu.features | grep -o PCID’ pic.twitter.com/C6aFBbaU8D
  • @internetofs**t Internet of S**t on x
    Here's a thread of AWS customers saying their CPU went to s**t when Amazon quietly patched this out this week https://forums.aws.amazon.com/ ...
  • @dinabass Dina Bass on x
    Intel says it sees no material impact to its business
  • @nicoleperlroth Nicole Perlroth on x
    3) Meltdown presents an urgent crisis and administrators need to implement the KAISER patch ASAP (even though it will slow performance speeds by as much as 30%), but the Spectre flaw is far more pervasive and will require a complete rearchitecture of virtually all microprocessors
  • @nicoleperlroth Nicole Perlroth on x
    1) The #IntelChip is only one piece of a much bigger security problem. There are two critical security flaws in microprocessors. The first, called Meltdown, affects virtually all Intel microprocessors.
  • @nicoleperlroth Nicole Perlroth on x
    2) The second, dubbed Spectre, is a design flaw that affects virtually all modern microprocessors (not just Intel, but AMD and ARM) and has NO PATCH.
  • @gossithedog Kevin Beaumont on x
    Reason I haven't commented on Intel CPU issue - detail is behind a non-disclosure, few people have signed it (incl me), there's little detail in public, erik's PoC people are highlighting is just a screenshot. Ultimately: it's patchable.
  • @suka_hiroaki Andreas Proschofsky on x
    Wow. What a highly unprofessional response. Angrily written counter-arguments to arguments nobody made. Also: PR spin galore. And oh: The media is totally evil. Suprised to see put out something like that by such a big company. http://twitter.com/...
  • @never_released Longhorn on x
    https://newsroom.intel.com/... “Recent reports that these exploits are caused by a “bug” or a “flaw” and are unique to Intel products are incorrect.” is wrong, it's at worst a KASLR bypass on other manufacturers, not a kernel memory read like Intel here.
  • @donal888 Don Clark on x
    Intel disputes the notion that there is a bug in its chips—cites research into software issues. But it is issuing fixes. http://newsroom.intel.com/...