AI coding tools are pretty good at finding bugs and make it easier and faster to fix them.
Importantly, security vulnerabilities in new releases seem to stay roughly the same and the change to which bugs count as CVEs was around version 6.8 already.
AI coding tools are pretty good at finding bugs and make it easier and faster to fix them.
Importantly, security vulnerabilities in new releases seem to stay roughly the same and the change to which bugs count as CVEs was around version 6.8 already.
It will be fascinating when the data is available, to see a graph showing the number of security vulnerabilities added to the kernel with each commit, obviously they’ll have to be found and patched before that can be determined.
I haven’t even looked at this yet but someone posted https://lwn.net/Articles/914632/ elsewhere in the thread, so sending it to you. As noted, less time to find in recent versions.
Maybe this https://aaddrick.github.io/kernel-cve-watch/data/cves.csv
(Not very well counted. Please double check my numbers. Ironically it made me wish I had mcp for LibreOffice because I couldn’t figure out how to sort this data correctly lmao)
282 introduced after 6.19 (including).
117 introduced before 6.19 (excluding) and fixed after 6.19. There’s also 31 fixed after 6.19 that don’t say when they were introduced.