If it's exploited, bad actors are capable of executing arbitrary code while evading detection due to a renamed process.
  • SomeGuy69@lemmy.worldEnglish
    0·
    13 days ago

    Urrg! I have one of those CPUs. (Exynos 9820) I don’t want to upgrade with an expensive new phone. I get no longer security updates.

      • corsicanguppy@lemmy.caEnglish
        1·
        11 days ago

        I’d try it, but this is essentially an emergency signalling device and not something I’d like to render inoperable.

        • Appoxo@lemmy.dbzer0.comEnglish
          1·
          10 days ago

          Certainly understandable. Wouldnt risk it on my current main device either. Only on a future new or old backup phone

    • sunzu2@thebrainbin.org
      01·
      13 days ago

      Pixel and grapheneos…

      About as good as normie can get currently

      Buy used to dent google direct profit and it is cheaper

        • sunzu2@thebrainbin.org
          0·
          13 days ago

          Custom roms dont require rooting. It is a bad security practice and not necessary.

          GrapheneOS uses sandboxed google play store and most banking apps work fine with exception like CashApp and other bankspy type shops.

          • Gerudo@lemm.eeEnglish
            0·
            13 days ago

            Is there a confirmed list of apps that will not function in Graphene? I searched around, and all I get is “some bank apps dont work” but your the first I see mention cashapp specifically. I could probably work around Cashapp, but I’d at least need zelle/venmo etc. Due to my credit union app more than likely not being compatible.

            I really want to move to the platform, but I don’t currently have a Pixel, so I can’t just try it out. Before going out, buying a Pixel, loading Graphene and finding out I can’t use my banking app or the very least the other money apps I’d just like a heads up.

            In the end if I need a backup phone then so be it.

  • linearchaos@lemmy.worldEnglish
    0·
    13 days ago

    Here’s the scope of it

    A National Institute of Standards and Technology (NIST) advisory on the bug describes it as “an issue [that] was discovered in the m2m scaler driver in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850, and W920.” A use-after-free bug in the mobile processor ultimately leads to privilege escalation, the agency added.