you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 week ago (5 children)

So could have Java, Go, C# or any language with GC. With garbage collection, the options object stays alive as long as any CPU holds a pointer to it, so use-after-free can't happen.

Besides, this exploit is so hard to pull off the only realistic outcome is a kernel panic, and that hasn't even been publicly demoed.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 1 week ago (4 children)

    So could have Java, Go, C# or any language with GC.

    No. Those aren't allowed in Linux Kernel.

    With garbage collection

    Garbage Collection is not usable in an operating system Kernel.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 1 week ago (3 children)

    Clearly, but it's worth pointing out that this kind of problem isn't uniquely fixed by "just use Rust".

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 week ago (2 children)

    I never said that only Rust prevents this. I just said using Rust in the Kernel would have prevented this issue.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 week ago (1 child)

    Fair enough. Don't you think it simplifies the issue a little bit? How long would it take to rewrite the entire TCP stack in rust?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 week ago

    I don't think a rewrite in Rust is necessary for everything that has a bug. Instead fixing the bug is probably more secure, before such alternative Rust code is mature enough to replace it.

  • source
  • parent