Originally posted by dc740
View Post
Announcement
Collapse
No announcement yet.
Further Analyzing The Intel CPU "x86 PTI Issue" On More Systems
Collapse
X
-
Originally posted by michalif bug dates back to Pentium days, I wonder how it's possible that it's discovered after 25 years. how many people knowed about it before? if it's so old and AMD didn't duplicated it, did they know about it?
Comment
-
Originally posted by pete910 View PostPatch for it being disabled for AMD has already been merged so No, Not default as its in rc release anyway. Even the arch guys have made sure the patch is in to.
I wonder why they don't have a general way of excluding processors. Having an if clause for one vendor seems stupid if there are many processors that are not affected by this. Maybe they are working on that or something.
Comment
-
-
Originally posted by carewolf View Post
Reading memory you are not allowed to could easily give you information to get privilege escalation.
Comment
-
Originally posted by carewolf View Post
No, there are two separate issues. The original issue that started investigation into such patches a year ago, and the issue that is causing a scramble now. AFAIK All modern CPU including AMDs are affected by the original issue, but it is more of theoretical thing that reveals a bit of data that can circumvent a secondary security measure. No OS would accept a heavy performance penalty for what is only a second-line security-by-obfuscation feature, so there is a new issue that only affects Intel CPUs. There is where the FUD comes in. Intel are trying to talk about the general vulnerability while the one everyone are and should only be concerned with is the Intel-specific one.
Comment
Comment