Greg K-H
gregkh
(not that it's not fun every year, but you get the idea...)
9
38
87
Stéphanie
Stephanie@thetransagenda.gay@gregkh What does this graph mean, then? Are new releases filled with bugs or does 7.0 coincide with a new generation of scanning tools?
1
0
0
@Stephanie @gregkh or new generation of generative tools? 😉
0
0
0
Josh Bressers
joshbressers@infosec.exchange@gregkh @KernelRecipes looks like 7.0 has more vulnerabilities than 6.0 :P
1
0
0
Stefan Eissing
icing@chaos.social@joshbressers @gregkh @KernelRecipes One never knows until they are found.🤷🏻♂️
0
0
0
0
0
3
1
5
5
@jeroen @gregkh @KernelRecipes the graph I really want is CVEs introduced per release
1
0
0
Greg K-H
gregkhHint, 5.15 is the leading "most CVEs created" kernel release for some reason...
0
1
2
0
0
1
I saw some graphs for curl, which did not only show count but also severity. And that revealed that even though the number of CVEs had gone up overall that was mostly due to lots of very low severity issues.
0
0
0
@gregkh Clearly as this graph shows, changing version Number to 7.x increased the number of CVEs. My recommendation would be to go back to 6.x. - even when this means, Linus has to add some more toes and fingers to his feet and hands to count the number after the dot. I think that price is acceptable for a more secure kernel. We all would benefit from this (and some additional fingers might come handy for Linus' guitar pedal soldering hobby :p )
@KernelRecipes
0
0
0
Christopher Evans
becomingwisest@hachyderm.io@gregkh Do long term kernel releases also patch CVEs? And does this graph track those fixes?
1
0
0
Greg K-H
gregkh
0
0
1
@gregkh @KernelRecipes is that CVE fixed or CVE found in the added code?
1
0
0
Edvin Malinovskis
nCrazed@fd00.space@gregkh @KernelRecipes will the talk include a graph of energy used per discovered CVE? 👀
1
0
0
Greg K-H
gregkh
0
0
0