<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cve on Danilo Falcão da Silva</title><link>https://falcao.org/tags/cve/</link><description>Recent content in Cve on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 23 May 2026 10:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/cve/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Bug Reports: The Real Vulnerability Is That We Weren't Looking Hard Enough</title><link>https://falcao.org/posts/ai-bug-discovery-revolution/</link><pubDate>Sat, 23 May 2026 10:00:00 -0300</pubDate><guid>https://falcao.org/posts/ai-bug-discovery-revolution/</guid><description>&lt;p>On May 18, 2026, Linus Torvalds called the Linux kernel security mailing list &lt;strong>&amp;ldquo;almost entirely unmanageable.&amp;rdquo;&lt;/strong> The reason: a flood of AI-generated bug reports. The reaction was predictable — ban AI, blame researchers, declare the tools aren&amp;rsquo;t ready.&lt;/p>
&lt;p>I &lt;a href="https://falcao.org/posts/ai-bug-reports-open-source/">wrote about the maintenance crisis last week&lt;/a> and I think that framing misses the deeper story. The problem is not that AI is generating too many reports. &lt;strong>The problem is that the code was more broken than we thought, and for twenty years nobody had the tools to look at it properly.&lt;/strong>&lt;/p></description></item></channel></rss>