Linux developers overwhelmed by AI-generated bug reports

Linux kernel developers are reportedly dealing with a rising number of AI-generated bug reports, creating extra work for maintainers and slowing down parts of the review process.
The issue is linked to users relying on large language models to automatically generate vulnerability reports and bug submissions and send them straight to maintainers. Although some of these reports point to legitimate issues, many are inaccurate, duplicated, or of too low-quality to be useful, forcing developers to spend additional time filtering real problems from false positives.
According to recent community discussions, maintainers across several open-source projects — including parts of the Linux ecosystem — say the volume of automated submissions has increased noticeably in recent months. Some developers have described the trend as “AI slop,” overwhelming issue trackers and review queues. What was already an issue a couple of years ago has now apparently gotten even worse.
Vulnerability workflows are also being affected
The growing number of AI-assisted submissions is also affecting vulnerability triage and bug bounty workflows. Since AI tools make it easier to produce large amounts of legit-looking reports, maintainers now face higher verification overhead and slower response times for genuinely critical issues.
The discussion has also drawn comments from Linus Torvalds, who has repeatedly criticized automated low-quality submissions that waste developers’ time.
Developers still see some value in AI tools
Some developers still see value in AI-assisted tools when they are used carefully and checked by humans, especially for spotting simple coding mistakes or potential vulnerabilities faster. The bigger problem, according to maintainers, is the growing amount of spam-like reports mixed in with legitimate submissions.
More broadly, the situation shows how AI is changing open-source development workflows. While these tools can help uncover bugs faster, they are also increasing the amount of time developers spend verifying reports and filtering out inaccurate submissions.




