> Why does the Linux kernel project continue to release code with flaws like this that can be found with automated tools?
Because they have no other option, it's a fuzzer. Therefore, it may take a long time(up to universe heat death) for it to finally exercise the path that causes the issue. And the kernel has a pretty enormous footprint.
Fuzzers never really terminate, so it is not like you can plug it on a CI/CD system and wait for reports.
> The process of reproducing one crash may take from a few minutes up to an hour depending on whether the crash is easily reproducible or non-reproducible at all.
That's for one known crash. But otherwise it will be running 24/7 (across multiple VMs!) looking for issues.
Because they have no other option, it's a fuzzer. Therefore, it may take a long time(up to universe heat death) for it to finally exercise the path that causes the issue. And the kernel has a pretty enormous footprint.
Fuzzers never really terminate, so it is not like you can plug it on a CI/CD system and wait for reports.
> The process of reproducing one crash may take from a few minutes up to an hour depending on whether the crash is easily reproducible or non-reproducible at all.
That's for one known crash. But otherwise it will be running 24/7 (across multiple VMs!) looking for issues.
More details here: https://github.com/google/syzkaller