<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Remember Spectre and Meltdown</title>
	<atom:link href="http://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Sat, 02 May 2026 07:48:22 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1854302</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 23 May 2025 12:37:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1854302</guid>
		<description><![CDATA[the most magical exploit i&#039;ve ever seen 
https://www.youtube.com/watch?v=9j_UzNtwZHg

Branch prediction? Never heard of her.

In this video we talk about a new vulnerability disclosed in every intel CPU that takes advantage of a hardware race condition in the intel processor&#039;s branch predictor.

Branch Privilege Injection: Compromising Spectre v2 Hardware
Mitigations by Exploiting Branch Predictor Race Conditions
https://comsec.ethz.ch/research/microarch/branch-privilege-injection/
https://comsec.ethz.ch/wp-content/files/bprc_sec25.pdf]]></description>
		<content:encoded><![CDATA[<p>the most magical exploit i&#8217;ve ever seen<br />
<a href="https://www.youtube.com/watch?v=9j_UzNtwZHg" rel="nofollow">https://www.youtube.com/watch?v=9j_UzNtwZHg</a></p>
<p>Branch prediction? Never heard of her.</p>
<p>In this video we talk about a new vulnerability disclosed in every intel CPU that takes advantage of a hardware race condition in the intel processor&#8217;s branch predictor.</p>
<p>Branch Privilege Injection: Compromising Spectre v2 Hardware<br />
Mitigations by Exploiting Branch Predictor Race Conditions<br />
<a href="https://comsec.ethz.ch/research/microarch/branch-privilege-injection/" rel="nofollow">https://comsec.ethz.ch/research/microarch/branch-privilege-injection/</a><br />
<a href="https://comsec.ethz.ch/wp-content/files/bprc_sec25.pdf" rel="nofollow">https://comsec.ethz.ch/wp-content/files/bprc_sec25.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1854132</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Thu, 22 May 2025 07:24:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1854132</guid>
		<description><![CDATA[Kaikista Intelin prosessoreista löytyi täysin uusi haavoittuvuus 
https://etn.fi/index.php/13-news/17553-kaikista-intelin-prosessoreista-loeytyi-taeysin-uusi-haavoittuvuus

Tietoturvatutkijat Sveitsin ETH Zürichin yliopistosta ovat löytäneet uuden, vakavan haavoittuvuuden Intelin prosessoreista. Kyseessä on täysin uusi haavoittuvuusluokka, jota kutsutaan nimellä Branch Privilege Injection. Se perustuu tapaan, jolla prosessorit ennakoivat tulevia laskentatehtäviä suorituskyvyn parantamiseksi.

Tutkijoiden mukaan haavoittuvuus mahdollistaa prosessin välisten suojausten ohittamisen ja koko keskusmuistin sisällön lukemisen pala kerrallaan. Tietojen vuotaminen tapahtuu nopeudella, joka on kaikkea muuta kuin teoreettinen: yli 5000 tavua sekunnissa, käytännössä hyökkääjä voi lukea koko muistin muutamassa minuutissa.

Haavoittuvuus koskee kaikkia Intelin prosessoreita, jotka on julkaistu vuodesta 2018 lähtien – niin henkilökohtaisissa tietokoneissa, kannettavissa kuin pilvipalvelinten suorittimissa. Tämä tekee uhasta erityisen vakavan erityisesti pilviympäristöissä, joissa useat käyttäjät jakavat saman laitteiston.

Nanosekuntien mittainen turva-aukko

Haavoittuvuus syntyy hetkellisesti, kun prosessori vaihtaa käyttäjien välillä. Juuri tässä siirtymässä ennakoivat laskennat voivat antaa hyökkääjälle mahdollisuuden päästä käsiksi toisen käyttäjän tietoihin. Kyse on nanosekunnin mittaisista ajoituksista, joita hyökkääjä voi toistaa yhä uudelleen ja lukea muistia tavu kerrallaan.

Tutkijoiden mukaan tämä ei ole yksittäinen ohjelmistovirhe, vaan osoitus syvemmistä ongelmista prosessoriarkkitehtuurissa, jotka juontavat juurensa spekulatiivisiin suorituskykytekniikoihin. Vastaavia haavoittuvuuksia ovat aiemmin olleet esimerkiksi Spectre, Meltdown ja Retbleed.

Intel on jo julkaissut mikrokoodipäivityksiä ongelman korjaamiseksi, ja käyttäjien suositellaan varmistavan, että kaikki käyttöjärjestelmä- ja BIOS-päivitykset on asennettu.]]></description>
		<content:encoded><![CDATA[<p>Kaikista Intelin prosessoreista löytyi täysin uusi haavoittuvuus<br />
<a href="https://etn.fi/index.php/13-news/17553-kaikista-intelin-prosessoreista-loeytyi-taeysin-uusi-haavoittuvuus" rel="nofollow">https://etn.fi/index.php/13-news/17553-kaikista-intelin-prosessoreista-loeytyi-taeysin-uusi-haavoittuvuus</a></p>
<p>Tietoturvatutkijat Sveitsin ETH Zürichin yliopistosta ovat löytäneet uuden, vakavan haavoittuvuuden Intelin prosessoreista. Kyseessä on täysin uusi haavoittuvuusluokka, jota kutsutaan nimellä Branch Privilege Injection. Se perustuu tapaan, jolla prosessorit ennakoivat tulevia laskentatehtäviä suorituskyvyn parantamiseksi.</p>
<p>Tutkijoiden mukaan haavoittuvuus mahdollistaa prosessin välisten suojausten ohittamisen ja koko keskusmuistin sisällön lukemisen pala kerrallaan. Tietojen vuotaminen tapahtuu nopeudella, joka on kaikkea muuta kuin teoreettinen: yli 5000 tavua sekunnissa, käytännössä hyökkääjä voi lukea koko muistin muutamassa minuutissa.</p>
<p>Haavoittuvuus koskee kaikkia Intelin prosessoreita, jotka on julkaistu vuodesta 2018 lähtien – niin henkilökohtaisissa tietokoneissa, kannettavissa kuin pilvipalvelinten suorittimissa. Tämä tekee uhasta erityisen vakavan erityisesti pilviympäristöissä, joissa useat käyttäjät jakavat saman laitteiston.</p>
<p>Nanosekuntien mittainen turva-aukko</p>
<p>Haavoittuvuus syntyy hetkellisesti, kun prosessori vaihtaa käyttäjien välillä. Juuri tässä siirtymässä ennakoivat laskennat voivat antaa hyökkääjälle mahdollisuuden päästä käsiksi toisen käyttäjän tietoihin. Kyse on nanosekunnin mittaisista ajoituksista, joita hyökkääjä voi toistaa yhä uudelleen ja lukea muistia tavu kerrallaan.</p>
<p>Tutkijoiden mukaan tämä ei ole yksittäinen ohjelmistovirhe, vaan osoitus syvemmistä ongelmista prosessoriarkkitehtuurissa, jotka juontavat juurensa spekulatiivisiin suorituskykytekniikoihin. Vastaavia haavoittuvuuksia ovat aiemmin olleet esimerkiksi Spectre, Meltdown ja Retbleed.</p>
<p>Intel on jo julkaissut mikrokoodipäivityksiä ongelman korjaamiseksi, ja käyttäjien suositellaan varmistavan, että kaikki käyttöjärjestelmä- ja BIOS-päivitykset on asennettu.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1853436</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 16 May 2025 05:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1853436</guid>
		<description><![CDATA[Endpoint Security
Chipmaker Patch Tuesday: Intel, AMD, Arm Respond to New CPU Attacks

Intel, AMD and Arm each published security advisories on Patch Tuesday, including for newly disclosed CPU attacks.

https://www.securityweek.com/chipmaker-patch-tuesday-intel-amd-arm-respond-to-new-cpu-attacks/

Chip giants Intel, AMD and Arm each published Patch Tuesday security advisories to inform customers about vulnerabilities found recently in their products, including ones related to newly disclosed CPU attacks.

One of the CPU attacks was disclosed this week by researchers at Swiss university ETH Zurich. The researchers discovered a branch privilege injection issue, tracked as CVE-2024-45332, that they claim “brings back the full might of branch target injection attacks (Spectre-BTI) on Intel”.

The researchers claim that while Intel’s Spectre-BTI (aka Spectre v2) mitigations have worked for nearly six years, they have now found a way to break them due to a race condition impacting Intel CPUs. 

Spectre-style attacks could allow an attacker who has access to the targeted system to obtain potentially valuable information from memory, such as encryption keys and passwords.

In its advisory, Intel said it’s releasing microcode updates to mitigate CVE-2024-45332, which it described as a sensitive information disclosure issue. 

AMD has published an advisory to inform customers that — as stated by the researchers as well — the vulnerability does not impact its CPUs. 

Another CPU attack was disclosed this week by researchers at Dutch university VU Amsterdam. Their analysis, dubbed Training Solo, led to the discovery of three new classes of self-training Spectre v2 attacks, which highlight the limitations of domain isolation.]]></description>
		<content:encoded><![CDATA[<p>Endpoint Security<br />
Chipmaker Patch Tuesday: Intel, AMD, Arm Respond to New CPU Attacks</p>
<p>Intel, AMD and Arm each published security advisories on Patch Tuesday, including for newly disclosed CPU attacks.</p>
<p><a href="https://www.securityweek.com/chipmaker-patch-tuesday-intel-amd-arm-respond-to-new-cpu-attacks/" rel="nofollow">https://www.securityweek.com/chipmaker-patch-tuesday-intel-amd-arm-respond-to-new-cpu-attacks/</a></p>
<p>Chip giants Intel, AMD and Arm each published Patch Tuesday security advisories to inform customers about vulnerabilities found recently in their products, including ones related to newly disclosed CPU attacks.</p>
<p>One of the CPU attacks was disclosed this week by researchers at Swiss university ETH Zurich. The researchers discovered a branch privilege injection issue, tracked as CVE-2024-45332, that they claim “brings back the full might of branch target injection attacks (Spectre-BTI) on Intel”.</p>
<p>The researchers claim that while Intel’s Spectre-BTI (aka Spectre v2) mitigations have worked for nearly six years, they have now found a way to break them due to a race condition impacting Intel CPUs. </p>
<p>Spectre-style attacks could allow an attacker who has access to the targeted system to obtain potentially valuable information from memory, such as encryption keys and passwords.</p>
<p>In its advisory, Intel said it’s releasing microcode updates to mitigate CVE-2024-45332, which it described as a sensitive information disclosure issue. </p>
<p>AMD has published an advisory to inform customers that — as stated by the researchers as well — the vulnerability does not impact its CPUs. </p>
<p>Another CPU attack was disclosed this week by researchers at Dutch university VU Amsterdam. Their analysis, dubbed Training Solo, led to the discovery of three new classes of self-training Spectre v2 attacks, which highlight the limitations of domain isolation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1838229</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sat, 26 Oct 2024 03:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1838229</guid>
		<description><![CDATA[When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.
Linus Torvalds explains why he&#039;s &quot;fed up with&quot; Intel, AMD, Nvidia and their &quot;buggy hardware&quot;
https://www.neowin.net/news/linus-torvalds-explains-why-hes-fed-up-with-intel-amd-nvidia-and-their-buggy-hardware/#google_vignette

Linus Torvalds, the father of Linux, is a fairly expressive person and his takes are almost always very interesting.

In a recent message on the Linux Kernel Mailing List (LKML) public inbox, Torvalds has been spotted showing his frustration about processor vulnerabilities as he said that he was &quot;pretty damn fed up with buggy hardware and completely theoretical attacks&quot; as he feels it is the job of the hardware vendors, the likes of Intel, AMD or Nvidia, to do better in finding theoretical attacks and vulnerabilities due to certain unaddressed and underlying hardware issues.

&quot;Honestly, I&#039;m pretty damn fed up with buggy hardware and completely theoretical attacks that have never actually shown themselves to be used in practice.

So I think this time we push back on the hardware people and tell them it&#039;s *THEIR* damn problem, and if they can&#039;t even be bothered to say yay-or-nay, we just sit tight.

Because dammit, let&#039;s put the onus on where the blame lies, and not just take any random shit from bad hardware and say &quot;oh, but it *might* be a problem&quot;.

Linus&quot;

Intel introduced LAM or Liner Address Masking with its 12th Gen Sapphire Rapids chips to improve memory safety

AMD&#039;s Upper Address Ignore (UAI) also works in a similar fashion and was introduced with the Zen 4 architecture or Ryzen 7000 series.

However, utilizing LAM makes a CPU vulnerable to speculation attacks also called SLAM (short for side-channel attacks via LAM) 

This is not the first time Linus Torvalds has complained against hardware companies over vulnerabilities. Back in 2023, the faulTPM CPU flaw on AMD Ryzen]]></description>
		<content:encoded><![CDATA[<p>When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.<br />
Linus Torvalds explains why he&#8217;s &#8220;fed up with&#8221; Intel, AMD, Nvidia and their &#8220;buggy hardware&#8221;<br />
<a href="https://www.neowin.net/news/linus-torvalds-explains-why-hes-fed-up-with-intel-amd-nvidia-and-their-buggy-hardware/#google_vignette" rel="nofollow">https://www.neowin.net/news/linus-torvalds-explains-why-hes-fed-up-with-intel-amd-nvidia-and-their-buggy-hardware/#google_vignette</a></p>
<p>Linus Torvalds, the father of Linux, is a fairly expressive person and his takes are almost always very interesting.</p>
<p>In a recent message on the Linux Kernel Mailing List (LKML) public inbox, Torvalds has been spotted showing his frustration about processor vulnerabilities as he said that he was &#8220;pretty damn fed up with buggy hardware and completely theoretical attacks&#8221; as he feels it is the job of the hardware vendors, the likes of Intel, AMD or Nvidia, to do better in finding theoretical attacks and vulnerabilities due to certain unaddressed and underlying hardware issues.</p>
<p>&#8220;Honestly, I&#8217;m pretty damn fed up with buggy hardware and completely theoretical attacks that have never actually shown themselves to be used in practice.</p>
<p>So I think this time we push back on the hardware people and tell them it&#8217;s *THEIR* damn problem, and if they can&#8217;t even be bothered to say yay-or-nay, we just sit tight.</p>
<p>Because dammit, let&#8217;s put the onus on where the blame lies, and not just take any random shit from bad hardware and say &#8220;oh, but it *might* be a problem&#8221;.</p>
<p>Linus&#8221;</p>
<p>Intel introduced LAM or Liner Address Masking with its 12th Gen Sapphire Rapids chips to improve memory safety</p>
<p>AMD&#8217;s Upper Address Ignore (UAI) also works in a similar fashion and was introduced with the Zen 4 architecture or Ryzen 7000 series.</p>
<p>However, utilizing LAM makes a CPU vulnerable to speculation attacks also called SLAM (short for side-channel attacks via LAM) </p>
<p>This is not the first time Linus Torvalds has complained against hardware companies over vulnerabilities. Back in 2023, the faulTPM CPU flaw on AMD Ryzen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1837707</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 18 Oct 2024 15:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1837707</guid>
		<description><![CDATA[Intel, AMD CPUs on Linux impacted by newly disclosed Spectre bypass
https://www.bleepingcomputer.com/news/security/intel-amd-cpus-on-linux-impacted-by-newly-disclosed-spectre-bypass/

The latest generations of Intel processors, including Xeon chips, and AMD&#039;s older microarchitectures on Linux are vulnerable to new speculative execution attacks that bypass existing ‘Spectre’ mitigations.

The vulnerabilities impact Intel&#039;s 12th, 13th, and 14th chip generations for consumers and the 5th and 6th generation of Xeon processors for servers, along with AMD&#039;s Zen 1, Zen 1+, and Zen 2 processors.

The attacks undermine the Indirect Branch Predictor Barrier (IBPB) on x86 processors, a core defense mechanism against speculative execution attacks.]]></description>
		<content:encoded><![CDATA[<p>Intel, AMD CPUs on Linux impacted by newly disclosed Spectre bypass<br />
<a href="https://www.bleepingcomputer.com/news/security/intel-amd-cpus-on-linux-impacted-by-newly-disclosed-spectre-bypass/" rel="nofollow">https://www.bleepingcomputer.com/news/security/intel-amd-cpus-on-linux-impacted-by-newly-disclosed-spectre-bypass/</a></p>
<p>The latest generations of Intel processors, including Xeon chips, and AMD&#8217;s older microarchitectures on Linux are vulnerable to new speculative execution attacks that bypass existing ‘Spectre’ mitigations.</p>
<p>The vulnerabilities impact Intel&#8217;s 12th, 13th, and 14th chip generations for consumers and the 5th and 6th generation of Xeon processors for servers, along with AMD&#8217;s Zen 1, Zen 1+, and Zen 2 processors.</p>
<p>The attacks undermine the Indirect Branch Predictor Barrier (IBPB) on x86 processors, a core defense mechanism against speculative execution attacks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1831497</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 03 Jul 2024 10:25:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1831497</guid>
		<description><![CDATA[Intel Says No New Mitigations Required for Indirector CPU Attack

Researchers disclosed a new high-precision Branch Target Injection attack method named Indirector, but Intel says no new mitigations are needed.

https://www.securityweek.com/intel-says-no-new-mitigations-required-for-indirector-cpu-attack/

A team of researchers from the University of California San Diego has published a paper detailing a novel attack method targeting Intel CPUs, but the chip giant says no new mitigations are required to address it. 

The new attack, named Indirector, is similar to the well-known Spectre v2 or Spectre Branch Target Injection (BTI) attack. 

These methods typically allow an attacker who has access to the targeted system to obtain information, including sensitive data such as passwords or encryption keys, from memory.  

The researchers described Indirector as a high-precision BTI attack that exploits the Indirect Branch Predictor (IBP) and the Branch Target Buffer (BTB) in high-end Intel CPUs such as Raptor Lake and Alder Lake. 

According to the researchers, previous BTI attacks overlooked IBP, which they describe as a “critical component of the branch prediction unit that predicts the target address of indirect branches”.  

https://indirector.cpusec.org/

This paper introduces novel high-precision Branch Target Injection (BTI) attacks, leveraging the intricate structures of the Indirect Branch Predictor (IBP) and the Branch Target Buffer (BTB) in high-end Intel CPUs (Raptor Lake and Alder Lake).]]></description>
		<content:encoded><![CDATA[<p>Intel Says No New Mitigations Required for Indirector CPU Attack</p>
<p>Researchers disclosed a new high-precision Branch Target Injection attack method named Indirector, but Intel says no new mitigations are needed.</p>
<p><a href="https://www.securityweek.com/intel-says-no-new-mitigations-required-for-indirector-cpu-attack/" rel="nofollow">https://www.securityweek.com/intel-says-no-new-mitigations-required-for-indirector-cpu-attack/</a></p>
<p>A team of researchers from the University of California San Diego has published a paper detailing a novel attack method targeting Intel CPUs, but the chip giant says no new mitigations are required to address it. </p>
<p>The new attack, named Indirector, is similar to the well-known Spectre v2 or Spectre Branch Target Injection (BTI) attack. </p>
<p>These methods typically allow an attacker who has access to the targeted system to obtain information, including sensitive data such as passwords or encryption keys, from memory.  </p>
<p>The researchers described Indirector as a high-precision BTI attack that exploits the Indirect Branch Predictor (IBP) and the Branch Target Buffer (BTB) in high-end Intel CPUs such as Raptor Lake and Alder Lake. </p>
<p>According to the researchers, previous BTI attacks overlooked IBP, which they describe as a “critical component of the branch prediction unit that predicts the target address of indirect branches”.  </p>
<p><a href="https://indirector.cpusec.org/" rel="nofollow">https://indirector.cpusec.org/</a></p>
<p>This paper introduces novel high-precision Branch Target Injection (BTI) attacks, leveraging the intricate structures of the Indirect Branch Predictor (IBP) and the Branch Target Buffer (BTB) in high-end Intel CPUs (Raptor Lake and Alder Lake).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1831060</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Thu, 27 Jun 2024 12:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1831060</guid>
		<description><![CDATA[Arm security defense shattered by speculative execution 95% of the time
&#039;TikTag&#039; security folks find anti-exploit mechanism rather fragile
https://www.theregister.com/2024/06/18/arm_memory_tag_extensions_leak/?td=keepreading

In 2018, chip designer Arm introduced a hardware security feature called Memory Tagging Extensions (MTE) as a defense against memory safety bugs. But it may not be as effective as first hoped.

Implemented and supported last year in Google&#039;s Pixel 8 and Pixel 8 Pro phones and previously in Linux, MTE aims to help detect memory safety violations, as well as hardening devices against attacks that attempt to exploit memory safety flaws.

Memory safety bugs are said to be responsible for the majority of security vulnerabilities in large codebases. And for the past few years, there&#039;s been a concerted effort in the public and private sector to reduce such flaws by promoting memory safe programming languages, software-based code hardening techniques, and hardware-specific options like SPARC ADI and Arm MTE.

MTE works by tagging blocks of physical memory with metadata. This metadata serves as a key that permits access. When a pointer references data within a tagged block of memory, the hardware checks to make sure the pointer contains a key matching that of the memory block to gain access to the data. A mismatch throws out an error.]]></description>
		<content:encoded><![CDATA[<p>Arm security defense shattered by speculative execution 95% of the time<br />
&#8216;TikTag&#8217; security folks find anti-exploit mechanism rather fragile<br />
<a href="https://www.theregister.com/2024/06/18/arm_memory_tag_extensions_leak/?td=keepreading" rel="nofollow">https://www.theregister.com/2024/06/18/arm_memory_tag_extensions_leak/?td=keepreading</a></p>
<p>In 2018, chip designer Arm introduced a hardware security feature called Memory Tagging Extensions (MTE) as a defense against memory safety bugs. But it may not be as effective as first hoped.</p>
<p>Implemented and supported last year in Google&#8217;s Pixel 8 and Pixel 8 Pro phones and previously in Linux, MTE aims to help detect memory safety violations, as well as hardening devices against attacks that attempt to exploit memory safety flaws.</p>
<p>Memory safety bugs are said to be responsible for the majority of security vulnerabilities in large codebases. And for the past few years, there&#8217;s been a concerted effort in the public and private sector to reduce such flaws by promoting memory safe programming languages, software-based code hardening techniques, and hardware-specific options like SPARC ADI and Arm MTE.</p>
<p>MTE works by tagging blocks of physical memory with metadata. This metadata serves as a key that permits access. When a pointer references data within a tagged block of memory, the hardware checks to make sure the pointer contains a key matching that of the memory block to gain access to the data. A mismatch throws out an error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1828469</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Thu, 23 May 2024 16:16:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1828469</guid>
		<description><![CDATA[https://travisdowns.github.io/blog/2021/06/17/rip-zero-opt.html
https://travisdowns.github.io/blog/2020/05/13/intel-zero-opt.html]]></description>
		<content:encoded><![CDATA[<p><a href="https://travisdowns.github.io/blog/2021/06/17/rip-zero-opt.html" rel="nofollow">https://travisdowns.github.io/blog/2021/06/17/rip-zero-opt.html</a><br />
<a href="https://travisdowns.github.io/blog/2020/05/13/intel-zero-opt.html" rel="nofollow">https://travisdowns.github.io/blog/2020/05/13/intel-zero-opt.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1827265</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 10 May 2024 16:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1827265</guid>
		<description><![CDATA[New Spectre-Style ‘Pathfinder’ Attack Targets Intel CPU, Leak Encryption Keys and Data
https://thehackernews.com/2024/05/new-spectre-style-pathfinder-attack.html

Researchers have discovered two novel attack methods targeting high-performance Intel CPUs that could be exploited to stage a key recovery attack against the Advanced Encryption Standard (AES) algorithm.

The techniques have been collectively dubbed Pathfinder by a group of academics from the University of California San Diego, Purdue University, UNC Chapel Hill, Georgia Institute of Technology, and Google.

“Pathfinder allows attackers to read and manipulate key components of the branch predictor, enabling two main types of attacks: reconstructing program control flow history and launching high-resolution Spectre attacks,” Hosein Yavarzadeh, the lead author of the paper, said in a statement shared with The Hacker News.

“Pathfinder allows attackers to read and manipulate key components of the branch predictor, enabling two main types of attacks: reconstructing program control flow history and launching high-resolution Spectre attacks,” Hosein Yavarzadeh, the lead author of the paper, said in a statement shared with The Hacker News.]]></description>
		<content:encoded><![CDATA[<p>New Spectre-Style ‘Pathfinder’ Attack Targets Intel CPU, Leak Encryption Keys and Data<br />
<a href="https://thehackernews.com/2024/05/new-spectre-style-pathfinder-attack.html" rel="nofollow">https://thehackernews.com/2024/05/new-spectre-style-pathfinder-attack.html</a></p>
<p>Researchers have discovered two novel attack methods targeting high-performance Intel CPUs that could be exploited to stage a key recovery attack against the Advanced Encryption Standard (AES) algorithm.</p>
<p>The techniques have been collectively dubbed Pathfinder by a group of academics from the University of California San Diego, Purdue University, UNC Chapel Hill, Georgia Institute of Technology, and Google.</p>
<p>“Pathfinder allows attackers to read and manipulate key components of the branch predictor, enabling two main types of attacks: reconstructing program control flow history and launching high-resolution Spectre attacks,” Hosein Yavarzadeh, the lead author of the paper, said in a statement shared with The Hacker News.</p>
<p>“Pathfinder allows attackers to read and manipulate key components of the branch predictor, enabling two main types of attacks: reconstructing program control flow history and launching high-resolution Spectre attacks,” Hosein Yavarzadeh, the lead author of the paper, said in a statement shared with The Hacker News.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2024/01/18/remember-spectre-and-meltdown/comment-page-1/#comment-1825686</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Tue, 16 Apr 2024 19:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=193131#comment-1825686</guid>
		<description><![CDATA[https://www.neowin.net/news/microsoft-shares-official-windows-registry-tweak-as-the-spectre-still-haunts-intel-in-2024/]]></description>
		<content:encoded><![CDATA[<p><a href="https://www.neowin.net/news/microsoft-shares-official-windows-registry-tweak-as-the-spectre-still-haunts-intel-in-2024/" rel="nofollow">https://www.neowin.net/news/microsoft-shares-official-windows-registry-tweak-as-the-spectre-still-haunts-intel-in-2024/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
