<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=5816&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Zenbleed - CVE-2023-20593]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=5816</link>
		<description><![CDATA[The most recent posts in Zenbleed - CVE-2023-20593.]]></description>
		<lastBuildDate>Wed, 26 Jul 2023 13:26:19 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Zenbleed - CVE-2023-20593]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=43052#p43052</link>
			<description><![CDATA[<p>I&#039;m not affected personally as my AMD 5600G is Zen3 not Zen2,</p><p>Nevertheless a AMD-microcode fix for Chimaera, Daedalus and Unstable landed this morning as a security update.</p><p>However as the end of that security-tracker (<a href="https://security-tracker.debian.org/tracker/CVE-2023-20593" rel="nofollow">https://security-tracker.debian.org/tra … 2023-20593</a>) it says:</p><div class="quotebox"><blockquote><div><p>3.20230719.1 ships the first batch of fixes, only for 2nd gen Epyc CPUs, further<br />CPUs to follow in later releases</p></div></blockquote></div><p>This is the one we have now got. Epyc is a database CPU.</p><p>So there are still fixes to come for the other Zen2 (Ryzen) CPUs which aren&#039;t fixed yet.</p><p>More info here:</p><p><a href="https://web.archive.org/web/20230724143835/https://lock.cmpxchg8b.com/zenbleed.html" rel="nofollow">https://web.archive.org/web/20230724143 … bleed.html</a></p><p>If you haven&#039;t got the microcode fix there is a workaround mentioned in this article:</p><div class="quotebox"><blockquote><div><p><span class="bbu">Workaround</span></p><p>It is highly recommended to use the microcode update.</p><p>If you can’t apply the update for some reason, there is a software workaround: you can set the chicken bit DE_CFG[9].</p><p>This may have some performance cost.</p><p>Linux</p><p>You can use msr-tools to set the chicken bit on all cores, like this:</p><p># wrmsr -a 0xc0011029 $(($(rdmsr -c 0xc0011029) | (1&lt;&lt;9)))</p></div></blockquote></div>]]></description>
			<author><![CDATA[dummy@example.com (Marjorie)]]></author>
			<pubDate>Wed, 26 Jul 2023 13:26:19 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=43052#p43052</guid>
		</item>
		<item>
			<title><![CDATA[Re: Zenbleed - CVE-2023-20593]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=43051#p43051</link>
			<description><![CDATA[<p>This is fixed in Devuan Chimaera....</p>]]></description>
			<author><![CDATA[dummy@example.com (stopAI)]]></author>
			<pubDate>Wed, 26 Jul 2023 11:10:36 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=43051#p43051</guid>
		</item>
		<item>
			<title><![CDATA[Zenbleed - CVE-2023-20593]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=43049#p43049</link>
			<description><![CDATA[<p>Thought i should post this in the interest of security.</p><div class="quotebox"><blockquote><div><p>An issue in “Zen 2” CPUs, under specific microarchitectural circumstances, may allow an attacker to potentially access sensitive information.</p></div></blockquote></div><p><a href="https://security-tracker.debian.org/tracker/CVE-2023-20593" rel="nofollow">https://security-tracker.debian.org/tra … 2023-20593</a></p><p>Interesting take from OpenBSD</p><p><a href="https://marc.info/?l=openbsd-tech&amp;m=169021508718971&amp;w=2" rel="nofollow">https://marc.info/?l=openbsd-tech&amp;m=169021508718971&amp;w=2</a></p>]]></description>
			<author><![CDATA[dummy@example.com (soren)]]></author>
			<pubDate>Wed, 26 Jul 2023 10:36:23 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=43049#p43049</guid>
		</item>
	</channel>
</rss>
