Here we are - 3600 which was still under manufacture 2-3 years ago are not get patched. Shame on you AMD, if it is true.

  • bruhduh@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    1 month ago

    Basically, reflash spi chips and it’ll be gone, and to be infected by that, person gotta have physical access to hardware he hacks, and physical access is root access as always has been

    • TheHolm@aussie.zoneOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      24 days ago

      Nope. You do not need physical access for it, just root access. and you HW is compromised with only means to recover it is SPI flashing of CPU.

  • blackstrat@lemmy.fwgx.uk
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 month ago

    Attackers need to access the system kernel to exploit the Sinkclose vulnerability, so the system would have to already be compromised. The hack itself is a sophisticated vector that is usually only used by state-sponsored hackers, so most casual users should take that into account.

    So it’s a vulnerability that requires you to.already have been compromised. Hardly seems like news.

    I can understand AMD only patching server chips that by definition will be under greater threat. On the other hand it’s probably not worth the bad publicity not to fix more.

    • Sethayy@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      That being said it builds up vulnerabilities in anti-cheats to another beautiful crowstrike like domino cluster fuck

    • PM_Your_Nudes_Please@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      It’s important because it allows them to directly modify the CPU’s microcode. Basically, the CPU has its own set of instructions, called microcode, which controls how the chip functions on a physical level. If they manage to change your microcode, even a full system reformat won’t kill the virus; You’ll need to either re-flash the CPU (which is not something the standard user or even power user will know how to do) or replace the entire CPU.

    • CaptPretentious@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      I personally agree. I think it’s being somewhat overhyped. If step one is physical access to get things rolling… like for sure some machines are in more public areas than others. But for me, someone would have to break into my house first, then access my machine, just to run exploits later. The exploit is pretty massive, but I think needs to be tempered with “first they need physical access”. Because physically controlling machines has always been number 1 for security.

    • atiredittechnician@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      1 month ago

      The reason that this is news is because it allows malware to embed itself into the processor microcode once kernel is breached. IE: If it is exploited for compromise, you either have to have the knowledge and hardware to reset the processor microcode manually (Requires an SPI flash tool) or you toss the hardware entirely. There’s no just ‘blow the drive away and reinstall the OS’ solution available.

      • WhyJiffie@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 month ago

        This sounds weird. I was in the impression that operating systems load updated cpu microcode at every boot, because it does not survive a power cycle, and because the one embedded in the BIOS/UEFI firmware is very often outdated. But then how exactly can a virus persist itself for practically forever?

        • Norah - She/They@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          1 month ago

          The OS can’t get to the point of loading cpu microcode without that outdated, embedded microcode. The reason it can persist is because there aren’t a lot of good ways to see what that UEFI microcode actually is once it’s installed. Plus, only the UEFI tells you that it has successfully updated itself. There is no other more authoritative system to verify that against. So the virus could just lie and say it’s gone and you would never know. Hence needing to treat it as the worst case scenario, that it never leaves.

      • booly@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        2
        ·
        1 month ago

        And that introduces a specific type of supply chain threat: someone who possesses a computer can infect their own computer, sell it or transfer it to the target, and then use the embedded microcode against the target, even if the target completely reformats and reinstalls a new OS from scratch.

        That’s not going to affect most people, but for certain types of high value targets they now need to make sure that the hardware they buy hasn’t already been infected in the supply chain.

  • narc0tic_bird@lemm.ee
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    1 month ago

    That’s so stupid, also because they have fixes for Zen and Zen 2 based Epyc CPUs available.

    Intel vs. AMD isn’t “bad guys” vs. “good guys”. Either company will take every opportunity to screw their customers over. Sure, “don’t buy Intel” holds true for 13th and 14th gen Core CPUs specifically, but other than that it’s more of a pick your poison.

    • haui@lemmy.giftedmc.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 month ago

      Tangent: If we started buying risc-v systems we might get to a point where they can actually compete.

      • PrivateNoob@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        That’s still far away from us as a consumer standpoint, but I’m eagerly waiting for a time when I could buy a RISC V laptop with atleast midrange computing capabalities

        • haui@lemmy.giftedmc.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 month ago

          I‘m more on the builder/tinkerer side so I‘m pretty much in starting position with risc-v now. But yes, its going to be some time before any of it is user ready as a pc.

        • haui@lemmy.giftedmc.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 month ago

          Yeah, thats the reason why we‘re in this capitalist hellhole. Perfection comes from billionaire money, nothing else.

            • haui@lemmy.giftedmc.com
              link
              fedilink
              English
              arrow-up
              0
              arrow-down
              1
              ·
              1 month ago

              I’m not buying hardware that doesn’t suit my needs as an investment hoping maybe it eventually will.

              You were misrepresenting things. Your needs have nothing to do with things not being functional. Something can be perfectly functional and not meet someones needs. Nobody said you should buy it as an investment.

    • Decipher0771@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      1 month ago

      “Both sides”

      “Vote third party!”

      Wtf seriously this isn’t the same thing remotely but the arguments used are.

    • Victor@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      2
      ·
      1 month ago

      How is AMD “screwing us over”? Surely they aren’t doing this on purpose? That seems very cynical.

      • Grippler@feddit.dk
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        1 month ago

        They are 100% not patching old chips intentionally by not allocating resources to it. It’s a conscious choice made by the company, it is very much “on purpose”.

        • Victor@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          2
          ·
          1 month ago

          That’s not what I was referring to. I was referring to the act of “adding vulnerabilities”. Surely they aren’t doing that on purpose. And surely they would add fixes for it if it was economically viable? It’s a matter of goodwill and reputation, right?

          I don’t know, I just don’t think it’s AMD’s business model to “screw over” their customers. I just don’t.

          • conciselyverbose@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 month ago

            The cost isn’t that high. They’re already doing it for a bunch of parallel systems.

            In a just world they’d be legally required to provide the fixes, or fully refund the entire platform cost. It’s not remotely ethical to allow this to exist unpatched anywhere, regardless of support life.

          • narc0tic_bird@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 month ago

            What I mean by that is that they will take a huge disservice to their customers over a slight financial inconvenience (packaging and validating an existing fix for different CPU series with the same architecture).

            I don’t classify fixing critical vulnerabilities from products as recent as the last decade as “goodwill”, that’s just what I’d expect to receive as a customer: a working product with no known vulnerabilities left open. I could’ve bought a Ryzen 3000 CPU (maybe as part of cheap office PCs or whatever) a few days ago, only to now know they have this severe vulnerability with the label WONTFIX on it. And even if I bought it 5 years ago: a fix exists, port it over!

            I know some people say it’s not that critical of a bug because an attacker needs kernel access, but it’s a convenient part of a vulnerability chain for an attacker that once exploited is almost impossible to detect and remove.

          • Grippler@feddit.dk
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 month ago

            No they are just choosing not to roll out the fix to a known issue, which is screwing customers over on purpose (to increase profits). It’s not a matter of goodwill, they sold a product that then turned out to have a massive security flaw, and now they don’t want to fix even though they absolutely could.

            • Victor@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              1 month ago

              I’m guessing it’s a balance between old products, effort, severity, etc. As we’ve learned, this is only an issue for an already infected system. 🤷‍♂️

              • Grippler@feddit.dk
                link
                fedilink
                English
                arrow-up
                0
                ·
                edit-2
                1 month ago

                Ryzen 3000 series CPUs are still sold as new, I even bought one six months ago, they’re no where near being classified as “old”, they’re hardly 5 years old. And this is not only an issue for already infected systems because uninfected systems will intentionally be left vulnerable.

                • Auli@lemmy.ca
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  29 days ago

                  Just because a store is still selling their stock doesn’t mean AND is still making them and selling them.

      • A_Random_Idiot@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        1 month ago

        I dont know.

        If I had my choice between a CPU that has a vulnerability that can only be exploited if the system is already compromised

        or a CPU that are full of oxidation cancer, or frying themselves and doing irreparable damage… Which the company is being excessively shady about concretely admitting to any RMA promises and wwill all eventually die in short order…

        I think I’m gonna go with the Ryzen and not leave leave my computer outside at defcon.

        • schizo@forum.uncomfortable.business
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          2
          ·
          1 month ago

          Sure but we’re talking about several generation old CPUs: nothing’s wrong with Intel’s 10/9/8th gen CPUs, which would be the contemporary ones to the Ryzen chips in question.

          • 486@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 month ago

            As much as I like RISC-V, it is kind of ironic to suggest RISC-V ist the solution to this. At least as it stands, because of RISC-V’s simplicity, most if not all current RISC-V CPUs don’t even run microcode, so there is nothing to update/fix in case of a CPU bug. There’s even a very current example of this problem with that chinese RISC-V cpu that has this “GhostWrite” bug that allows every unpriviliged process to gain root access.

            • WhyJiffie@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 month ago

              As I said in an other reply, RISC-V is not the solution for the reason that they are perfect today. It is because it is not limited to being used by a few megacorporations that do whatever they want, but it allows competition where companies do what they need to become and remain a good choice.

              • 486@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 month ago

                I understood that. My point was rather that in this particular case (a CPU bug that could be fixed via microcode, but AMD chose not to do so for certain CPUs), RISC-V wouldn’t have been of any advantage, because there would be nothing to fix in the first place. Sure, one could introduce microcode for RISC-V and people have argued in favor of doing so for this exact reason, but the architecture was intentionally designed to not require microcode.

  • Harvey656@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 month ago

    So I have a 3700x, I’ve read about the vulnerability but don’t fully understand it. How at risk am I?

    • ozymandias117@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      edit-2
      1 month ago

      If an attacker gets access to your system, they will be able to ensure you can’t get rid of their access

      It will persist across operating system installs

      However, this requires them to get access first

      • Harvey656@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        Sounds like it’s time for an upgrade. Never know what kind of weirdos are out there. Thanks for the information.

    • psmgx@lemmy.world
      cake
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 month ago

      If they get root or admin they can hack the chip itself.

      But minor exploits, nada, no issue, you good. Gotta get root to make it happen.

      Problem is if you, as they say, get got, you have no way of knowing if they’re in your CPU, and no way to fix if they did – basically gotta trash it and replace.

    • ulterno@lemmy.kde.social
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      3
      ·
      edit-2
      1 month ago

      In short, if you’re pwned once, you are pwn3d f0r3v#rrrrreeeheehaahaahaa*cough**cough*


      These are the kinds of exploits you use to create APT (Advanced Persistent Threats).

    • ducking_donuts@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      The good news is that in order to exploit the new vulnerability, the attacker first has to obtain kernel level access to the system somehow - by exploiting some other vulnerabilities perhaps.

      The bad news is once Sinkclose attack is performed, it can be hard to detect and mitigate: it can even survive an OS reinstall.

      • scoutFDT@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        So basically what you are saying is we just need one pvp game with kernel level anti cheat to fuck up somewhere… yeah I’m sure that’s not going to happen.

        • raspberriesareyummy@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          1 month ago

          we just need one pvp game with kernel level anti cheat

          Leaving aside that security patches should be done, if you install that kind of game on a system where you have any data worth protecting, you’re a dumb ass mtherfcker. Sorry, but seriously, that’s just how it is.

      • JASN_DE@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        1 month ago

        The other bad news: there are so many vulnerabilities on all systems which can be used to gain root-level access, it’s just a matter of time. Also, even future vulnerabilities will be an issue, as the underlying Sinkclose attacks will still work.

    • TheHolm@aussie.zoneOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 month ago

      You need to be a root to exploit it, but if it get exploited any way to get rid of it is to throw MB to trash.

        • Vash63@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          1 month ago

          How do you trust that the flash was done properly if you did it from the compromised system? This would only work if you flashed it externally somehow without the system running.

  • ipkpjersi@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    1 month ago

    Yay, another BIOS update!

    I am getting so sick of all these BIOS updates because of all these security vulnerabilities all the time. It is so tiring having to set up my settings all over again all of the time. Earlier this year, or maybe it was last year, it felt like every month or two there was a new BIOS update for a new security vulnerability.

      • ipkpjersi@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        1 month ago

        Depending on your BIOS and/or motherboard, you can’t restore them between versions. The point of clearing the BIOS settings after flashing a new version is to ensure that you only have values that are expected, which is why restoring backups can often be blocked between versions.

  • punkfungus@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    1 month ago

    Really not good enough from AMD. I wonder if Intel wasn’t a complete dumpster fire right now if they would still cut off the fix at Zen 3 (I doubt it). There’s really no reason not to issue a fix for these other than they don’t want to pay the engineers for the time to do it, and they think it won’t cost them any reputational damage.

    I hate that every product and company sucks so hard these days.

    • kibiz0r@midwest.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      They did issue a fix: “Buy a new CPU please!”

      That’s why they don’t mind the reputation hit. If 1 person swears allegiance to Intel as a result but 2 people buy new AMD chips, they’re still ahead. And people will forget eventually. But AMD won’t forget the Q3 2024 sales figures.

      • ulterno@lemmy.kde.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 month ago

        Well, guess who’s not buying next gen Ryzen?

        They are doing similar stuff with deliberately delaying Linux driver capabilities for Radeon 7xxx series, to make more GPUs die out faster, by overheating (zero RPM fan until 60°+).

    • nlgranger@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 month ago

      Consumer usage is not really concerned by the attack scenario of this vulnerability from what I understand. The prerequisite is to have access to the bios so it’s already game over at this point.

      • WhyJiffie@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        2
        ·
        1 month ago

        Chip makes should not only treat customer CPUs as possibly-business hardware when adding shit like (Intel) ME, Pluton and (AMD) PSP, but also when patching serious vulnerabilities and providing support!

        • hangonasecond@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          When you pay for enterprise equipment, you are typically paying a premium for longer, more robust support. Consumer products are less expensive because they don’t get this support.

          • WhyJiffie@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            arrow-down
            1
            ·
            1 month ago

            But they are already pretending for whatever reason that these are suitable for enterprises, by always includingthe aformentioned remote control components!

        • nlgranger@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 month ago

          Agreed, firmware security by chip manufacturers has been underwhelming to say the least and we can blame them for that. But in this specific instance I still don’t see the benefit of a fix for consumer usage. Companies have a responsibility and accountability toward their users, so a fix is due, for personal laptops/PCs the threat is toward the owners themselves (activists, diplomats, journalists, etc.). The latter do not buy second hand equipment, and if the firmware is compromised while they own it, they are already in danger.

          • WhyJiffie@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            1 month ago

            The latter do not buy second hand equipment

            You are assuming activists are well funded in some way, and that they are not repressed.

            This obviously has a benefit for consumer usage too, same as encryption. You’re basically saying consumers don’t need any kind of antivirus either, because it’s not that critical.
            This vuln should have been fixed for consumer hardware too, because it basically permanently taints all hardware that is vulnerable to it. And what makes it so hard to release patches for consumer hardware, when patches were already made for the same generations of enterprise hardware? Basically the majority of the work has been done already

            • nlgranger@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              25 days ago

              I’m not saying this is a small issue and nothing should be done. I just noted that the issue is not as big as some other hardware-based vulnerabilities we encountered in the past. And every threat model calls for a corresponding counter-measure.

              You are assuming activists are well funded in some way, and that they are not repressed. I’m assuming they are repressed, which is why they have people that buy and configure their equipment and hand it to them so that it hasn’t been tampered with. If you cannot afford that your should use your computer as if it was compromised.

              You’re basically saying consumers don’t need any kind of antivirus either Where did I write that?

              And what makes it so hard to release patches for consumer hardware. AMD focusing on where its money’s at and OEM/motherboard manufacturers being cheap and lazy and not pushing forward updates when they have them.

  • teawrecks@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 month ago

    I feel like this is the perfect place for Right to Repair legislation: the product is broken? And it’s outside your support window? Then give customers what they need to make the fix themselves. It’s not good enough to say “meh, guess you gotta buy one of our newer chips then 🤷”

  • Eskuero@lemmy.fromshado.ws
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    lol for the past 15 years I have “rebuilt” my desktop every 5 years but I didn’t expect the would try to force me out of my 7 3700x right on the date

      • dinckel@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        At launch, I’ve upgraded my system to a 3900x, and even today, it fulfills my cpu needs. This thing is incredible

        • Microplasticbrain@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          Yea i got the 3900xt when i built my pc during covid. Love it but i had to disable a bunch of shit to prevent bluescreens from hypervisor shit

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    24 days ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    IP Internet Protocol
    NAS Network-Attached Storage
    SSD Solid State Drive mass storage

    3 acronyms in this thread; the most compressed thread commented on today has 4 acronyms.

    [Thread #919 for this sub, first seen 12th Aug 2024, 20:35] [FAQ] [Full list] [Contact] [Source code]

  • BrightCandle@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    1 month ago

    AMD has unfortunately a long history of abandoning products before its reasonable on its graphics division. Its not really acceptable, up until earlier this year my NAS/server was running a 3600 and its only for power saving purposes I changed that as its still a very workable CPU in that role.