Same analogy... there's a vulnerability and you want to test it? Go set up a test, and notify the people.
You really think the Linux kernel guys would change their process if you did this? They'd still do the same things they do.
You really think the Linux kernel guys would change their process if you did this? They'd still do the same things they do.
The vulnerability is in the process, and this was the test.
> You really think the Linux kernel guys would change their process if you did this? They'd still do the same things they do.
If they're vulnerable to accepting patches with exploits because the review process fails, then the process is broken. Linux isn't some toy, it's critical infrastructure.
No, you can't, because that is the test! If you manage to push exploits to the real kernel, the test failed. If you get caught, the test passes. They did get caught.
If they don't, then that's the vulnerability in the process.
That's what they do every time.
The best they can do is notify the maintainers after they got the result for their research and give the maintainers an easy way to recover from vulnerability they intentionally create.