• CountVon@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    59
    ·
    3 days ago

    This article is more than little silly, at least for the target audience. These security vulnerabilities are of great concern to system administrators, but it’s overblown to say that Linux gamers everywhere need to worry about these. The two remote code execution vulnerabilities are only a concern if you’re running a ksmbd server. Who’s running a Windows-protocol file server on their Steam Deck?? C’mon now…

    • queeradjacent@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      25
      ·
      3 days ago

      Beat me to it, what exactly is the attack vector on my Steam Deck that mostly sleeps and is on a limited segment behind my firewall and is only used for games 🙄

    • black0ut@pawb.social
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      It is also not immediately dangerous to run ksmbd, as 99.9% of users aren’t exposing a SMB share to the internet. Most of them will be shared through a LAN at most, and even on enterprise solutions they’re only accessed through a VPN.

      It’s definitely an issue for lateral movement through a network once it’s infected, but that’s not something regular users should worry about, for the most part.

      Of course, apply the patch once it’s available, but yeah, this is mostly a nothingburger.