←back to thread

239 points r4um | 1 comments | | HN request time: 0s | source
Show context
charcircuit ◴[] No.45113673[source]
>Convinced the path forward would be painful, I shelved the bug.

As opposed to fixing the bug? Either the incentives are broken for security researchers to fix bugs, contributing fixes to Linux is broken, or both.

A rewrite of these user interactable subsystems in Rust can't come soon enough.

replies(4): >>45113715 #>>45113831 #>>45113876 #>>45114005 #
pdw ◴[] No.45113831[source]
Security researchers rarely fix bugs. They don't see it as their job, and it requires a very different skill set than finding or exploiting them anyway.
replies(2): >>45113915 #>>45114734 #
TheDong ◴[] No.45113915[source]
This is misplaced in this case.

The author mentioned CVE-2021-26708, which is very similar to this bug, and in fact the author both exploited it and authored the upstream fix in the kernel.

> and it requires a very different skill set than finding or exploiting them anyway

I disagree with that. Exploiting bugs is really hard, and if you can exploit them, you absolutely know enough about the kernel in order to patch it.

Sure, architecting a kernel, making code maintainable, that's a software engineering skill. But fixing a use-after-free? That's easier than exploiting it, of course they can fix it.

replies(1): >>45114130 #
Den_VR ◴[] No.45114130[source]
There’s the technical challenge, and then there’s the process challenge.
replies(1): >>45114352 #
account42 ◴[] No.45114352[source]
Sending an email with a simple patch is not a challenge.
replies(1): >>45114633 #
brookst ◴[] No.45114633[source]
Thanks for submitting the fix here!
replies(1): >>45124587 #
1. account42 ◴[] No.45124587[source]
You might want to read the thread you are responding to instead of posting knee-jerk reactions.