top 18 comments

sorted by: hot top controversial new old
[–] 53 points 6 months ago (1 child)
  • [–] 19 points 6 months ago

    Good news. One fewer zero-day.

  • source
  • [–] 14 points 6 months ago (1 child)

    I'm sure removing the root user will prevent all escalation exploits. Can't get root if there is no root!

    /j

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 14 points 6 months ago (1 child)

    Same workaround works here as with dirty frag. Just disable those kernel modules.

  • source
  • hideshow 1 child comment
  • load more comments (-1 replies)
    [–] 15 points 6 months ago (3 children)

    If this is quickly solved, there is nothing to worry about

    Sorry if my english is bad

  • source
  • hideshow 3 child comments
  • [–] 7 points 6 months ago

    apparmor ftw

  • source
  • [–] 7 points 6 months ago (1 child)

    At this point we might as well just run everything as root anyway

  • source
  • hideshow 1 child comment
  • [–] 6 points 6 months ago (1 child)

    what's a scenario where you could suffer from this vulnerability?

  • source
  • hideshow 1 child comment
  • [–] 3 points 6 months ago

    Scarry! Uoi guys on windows better stay away...ohhh privilege!

  • source
  • [–] 3 points 6 months ago

    I think you might be able to deactivate this one by turning off XFRM support in a custom-configured kernel, at the cost of losing some types of tunneling. Not going to actually test that, though.

  • source
  • 2 comments in c/linux@programming.dev view that post
    [–] 14 points 6 months ago

    However, it is in the same surface and the mitigation is the same as for dirtyfrag.

    phew

  • source
  • [–] 4 points 6 months ago*

    Where's the CVE? Was there an attempt at responsible disclosure? Was confidentiality breached? Did they coordinate this release with the devs like the dirtyfrag people did? This "announcement" doesn't answer any of these questions and I am frustrated by it.

    EDIT: Ok, there IS a CVE: https://security-tracker.debian.org/tracker/CVE-2026-46300

  • source