Intel fails to get Spectre, Meltdown chip flaw class-action super-suit tossed out
(2022/01/28)
- Reference: 1643332689
- News link: https://www.theregister.co.uk/2022/01/28/intel_spectre_lawsuit/
- Source link:
Intel will have to defend itself against claims that the semiconductor goliath knew its microprocessors were defective and failed to tell customers.
On Wednesday, Judge Michael Simon, of the US District Court of Oregon, partially denied the tech giant's motion to dismiss a class-action lawsuit arising from the 2018 public disclosure of Meltdown and Spectre, the family of data-leaking chip microarchitecture design blunders.
The Register [1]broke the Meltdown story on January 2, 2018, as Intel and those who confidentially reported the security vulnerabilities were preparing to disclose them. The following day, Google's Project Zero [2]published details of Meltdown and its cousin Spectre, revealing that efforts to make CPU cores faster using speculative execution have opened them up to side-channel attacks that can read memory that should be out of reach and leak confidential information.
[3]
To defend against Meltdown and Spectre, Intel and other affected vendors have had to add software and hardware mitigations that for some workloads make patched processors mildly to significantly slower.
[4]
[5]
The disclosure of related flaws has continued since that time, as researchers develop variations on the initial attacks and find other parts of chips that similarly expose privileged data. It is a problem that still is not entirely solved.
Intel, as the largest x86 microprocessor maker, has been the most affected by the findings: its chips were vulnerable to both Meltdown (along with Arm Cortex-A75 and IBM POWER) and Spectre, whereas rivals like AMD were affected only by Spectre. Thus Intel is the focus of much litigation: the biz [6]faced 32 lawsuits only a month after the vulnerabilities were publicly acknowledged.
[7]
Those lawsuits have been consolidated into a multi-district proceeding known as "Intel Corp. CPU Marketing, Sales Practices and Products Liability Litigation" (3:18-md-02828-SI). And since 2018, Intel has been trying to get them to go away.
Twice before the judge had dismissed the plaintiffs' complaint while allowing the plaintiffs to amend and refile their allegations. This third time, the judge only partially granted Intel's motion to toss the case.
Judge Simon dismissed claims based on purchases up through August 2017 because Intel was unaware of the microarchitecture vulnerabilities up to that point. But he allowed seven claims, from September 2017 onward, to proceed, finding the plaintiffs' contention that Intel delayed disclosure of the flaws to maximize holiday season sales plausible enough to allow the case to move forward.
[8]
"Based on plaintiffs' allegations, it is not clear that Intel had a countervailing business interest other than profit for delaying disclosure for as long as it did (through the holiday season), for downplaying the negative effects of the mitigation, for suppressing the effects of the mitigation, and for continuing to embargo further security exploits that affect only Intel processors," the judge wrote in his order
"For the seven plaintiffs who purchased computers after September 1, 2017, they have alleged enough facts at this stage of the proceedings to survive Intel's motion to dismiss on the grounds of failure to state a claim."
[10]Intel's recent Atom, Celeron, Pentium chips can be lulled into a debug mode, potentially revealing system secrets
[11]When the world ends, all that will be left are cockroaches and new Rowhammer attacks: RAM defenses broken again
[12]Boffins find if you torture AMD Zen+, Zen 2 CPUs enough, they are vulnerable to Meltdown-like attack
[13]Please, no Moore: 'Law' that defined how chips have been made for decades has run itself into a cul-de-sac
The case isn't yet destined for trial as there are more procedural steps along that road. The likely off-ramp for Intel, in the absence of further procedural defenses, would be a settlement – a trial runs the risk of a significant damage award.
"We are pleased with the Court's decision, which found that the claims we allege show Intel 'took advantage of consumers' lack of knowledge such that the resulting unfairness was glaringly noticeable, flagrant, complete, and unmitigated,' said Christopher Seeger, an attorney with Seeger Weiss LLP, who is lead counsel for the plaintiffs, in an emailed statement.
"We look forward to advancing this litigation on behalf of consumers and businesses that were left with slower and less secure computers due to the defects found in Intel's processors."
Intel declined to comment. ®
Get our [14]Tech Resources
[1] https://www.theregister.com/2018/01/02/intel_cpu_design_flaw/
[2] https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://www.theregister.com/2018/02/17/intel_says_32_suits_filed/
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[9] https://regmedia.co.uk/2022/01/27/intel_motion.pdf
[10] https://www.theregister.com/2021/11/16/intels_chip_flaw/
[11] https://www.theregister.com/2021/11/15/rowhammer_blacksmith_memory/
[12] https://www.theregister.com/2021/08/30/amd_meltdown_zen/
[13] https://www.theregister.com/2021/08/05/moores_law_what_next/
[14] https://whitepapers.theregister.com/
On Wednesday, Judge Michael Simon, of the US District Court of Oregon, partially denied the tech giant's motion to dismiss a class-action lawsuit arising from the 2018 public disclosure of Meltdown and Spectre, the family of data-leaking chip microarchitecture design blunders.
The Register [1]broke the Meltdown story on January 2, 2018, as Intel and those who confidentially reported the security vulnerabilities were preparing to disclose them. The following day, Google's Project Zero [2]published details of Meltdown and its cousin Spectre, revealing that efforts to make CPU cores faster using speculative execution have opened them up to side-channel attacks that can read memory that should be out of reach and leak confidential information.
[3]
To defend against Meltdown and Spectre, Intel and other affected vendors have had to add software and hardware mitigations that for some workloads make patched processors mildly to significantly slower.
[4]
[5]
The disclosure of related flaws has continued since that time, as researchers develop variations on the initial attacks and find other parts of chips that similarly expose privileged data. It is a problem that still is not entirely solved.
Intel, as the largest x86 microprocessor maker, has been the most affected by the findings: its chips were vulnerable to both Meltdown (along with Arm Cortex-A75 and IBM POWER) and Spectre, whereas rivals like AMD were affected only by Spectre. Thus Intel is the focus of much litigation: the biz [6]faced 32 lawsuits only a month after the vulnerabilities were publicly acknowledged.
[7]
Those lawsuits have been consolidated into a multi-district proceeding known as "Intel Corp. CPU Marketing, Sales Practices and Products Liability Litigation" (3:18-md-02828-SI). And since 2018, Intel has been trying to get them to go away.
Twice before the judge had dismissed the plaintiffs' complaint while allowing the plaintiffs to amend and refile their allegations. This third time, the judge only partially granted Intel's motion to toss the case.
Judge Simon dismissed claims based on purchases up through August 2017 because Intel was unaware of the microarchitecture vulnerabilities up to that point. But he allowed seven claims, from September 2017 onward, to proceed, finding the plaintiffs' contention that Intel delayed disclosure of the flaws to maximize holiday season sales plausible enough to allow the case to move forward.
[8]
"Based on plaintiffs' allegations, it is not clear that Intel had a countervailing business interest other than profit for delaying disclosure for as long as it did (through the holiday season), for downplaying the negative effects of the mitigation, for suppressing the effects of the mitigation, and for continuing to embargo further security exploits that affect only Intel processors," the judge wrote in his order
[9]PDF
."For the seven plaintiffs who purchased computers after September 1, 2017, they have alleged enough facts at this stage of the proceedings to survive Intel's motion to dismiss on the grounds of failure to state a claim."
[10]Intel's recent Atom, Celeron, Pentium chips can be lulled into a debug mode, potentially revealing system secrets
[11]When the world ends, all that will be left are cockroaches and new Rowhammer attacks: RAM defenses broken again
[12]Boffins find if you torture AMD Zen+, Zen 2 CPUs enough, they are vulnerable to Meltdown-like attack
[13]Please, no Moore: 'Law' that defined how chips have been made for decades has run itself into a cul-de-sac
The case isn't yet destined for trial as there are more procedural steps along that road. The likely off-ramp for Intel, in the absence of further procedural defenses, would be a settlement – a trial runs the risk of a significant damage award.
"We are pleased with the Court's decision, which found that the claims we allege show Intel 'took advantage of consumers' lack of knowledge such that the resulting unfairness was glaringly noticeable, flagrant, complete, and unmitigated,' said Christopher Seeger, an attorney with Seeger Weiss LLP, who is lead counsel for the plaintiffs, in an emailed statement.
"We look forward to advancing this litigation on behalf of consumers and businesses that were left with slower and less secure computers due to the defects found in Intel's processors."
Intel declined to comment. ®
Get our [14]Tech Resources
[1] https://www.theregister.com/2018/01/02/intel_cpu_design_flaw/
[2] https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://www.theregister.com/2018/02/17/intel_says_32_suits_filed/
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YfN4hrz9mBvSe8o5x7ZnngAAAAc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[9] https://regmedia.co.uk/2022/01/27/intel_motion.pdf
[10] https://www.theregister.com/2021/11/16/intels_chip_flaw/
[11] https://www.theregister.com/2021/11/15/rowhammer_blacksmith_memory/
[12] https://www.theregister.com/2021/08/30/amd_meltdown_zen/
[13] https://www.theregister.com/2021/08/05/moores_law_what_next/
[14] https://whitepapers.theregister.com/
Re: Defective?
diodesign
IMHO it's possible to argue that Meltdown was a defect because Intel trivially broke one or more of the data security guarantees it gave in its documentation (IIRC, it's been a while so ICBW).
Spectre's a bit different IMHO because while it could be exploited to leak data, it was more like discerning info through instrumentation.
Whereas, Meltdown was as simple as placing a load after a branch instruction and seeing if the load was speculatively executed even if the branch was taken. And it was found that the speculative load occurred before security checks were performed, allowing one to figure out the content of memory that would have been trapped if read directly.
AIUI the chap who found Meltdown - a Googler straight out of uni - read the Intel soft dev manual, saw the part that said if a branch is taken, the CPU won't execute the instructions that follow immediately after the branch, and thought, 'yeah but I wonder if it does?'
Meltdown to me looked trivial to exploit, just a straight up bug in the design of the pipeline. Spectre looked more nuanced: a side effect of other optimizations.
As I said, ICBW.
C.
CEO Share sales
TReko
don't forget Intel's management team sold many of their share options just before the news was released, too.
Just a co-incidence, I'm sure...
Re: CEO Share sales
DS999
Insiders generally file paperwork with share sale plans ahead of time, so if they'd already filed months in advance it may not be as bad as it looks. Sometimes they file these plans even when they aren't required to just to avoid any implication of insider trading as the SEC considers that an affirmative defense.
Defective?
This isn't like that Pentium multiply bug from decades ago. That was a proper bug. This is exploiting the properties of caches in an obscure, abstract, and higly creative way to get information about data that arguably shouldn't be in cached RAM in the first place.
The people who file lawsuits like this may just be opportunists looking to feed off a carcass (or endless legal work) but ultimately it comes down to the overall ignorance of our society about the capabilities and limitations of computers, an ignorance characterized by a have it all expectations with a demand for compensation when they don't get it.