this post was submitted on 26 Oct 2026
142 points (93.3% liked)

Linux

15321 readers
241 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS
 

Source: https://github.com/gregkh/kernel-development/blob/master/graphs%2Fpatches_per_release%2Fcves_fixed_per_release.png

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.

you are viewing a single comment's thread
view the rest of the comments
[–] ShutUpWesley@piefed.zip 36 points 2 days ago (2 children)

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.

[–] daychilde@lemmy.world 3 points 2 days ago

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.

[–] Aria@lemmygrad.ml 2 points 2 days ago

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.