As I mentioned, all kernel major releases have cve bumps, because (also mentioned) new kernel releases have new features and drivers.
The bump itself doesn’t show that ai is associated with more CVEs, because that bump is present after every kernel major release. It would have been better to show the bumps from previous releases to demonstrate the volume ai tools are helping to find.
That’s not how the version numbers for the Linux kernel work. 7.0 is the release that follows 6.19, they are both new mainline releases in the exact same way, and the first number increasing doesn’t mean anything.
But we don’t have enough information here; it says “CVE fixes per release”, we don’t know anything about them. Are these long-standing? Is some new process introducing security issues? We also have ongoing conversions of modules to rust, and lots of ongoing work.
We can say AI tools are helping find these, and that may be true, but but this graph doesn’t say that, it just says “CVE Number Big”.
How is it misleading? All you’ve said is that releases have cves which is what the graph shows.
As I mentioned, all kernel major releases have cve bumps, because (also mentioned) new kernel releases have new features and drivers.
The bump itself doesn’t show that ai is associated with more CVEs, because that bump is present after every kernel major release. It would have been better to show the bumps from previous releases to demonstrate the volume ai tools are helping to find.
That’s not how the version numbers for the Linux kernel work. 7.0 is the release that follows 6.19, they are both new mainline releases in the exact same way, and the first number increasing doesn’t mean anything.
Yes, acknowledged. I see the point some ppl were trying to make.
By “bump” you mean the quadrupling of CVEs being addressed?
Or being introduced. Or neither of those two, because it’s an isolated graph devoid of larger context
Yes, this is the point I was trying to make, there is no context.
It’s “being discovered”. You need context? Here: https://zerodayclock.com/#where-the-vulnerability-exposure-is-growing
But we don’t have enough information here; it says “CVE fixes per release”, we don’t know anything about them. Are these long-standing? Is some new process introducing security issues? We also have ongoing conversions of modules to rust, and lots of ongoing work.
We can say AI tools are helping find these, and that may be true, but but this graph doesn’t say that, it just says “CVE Number Big”.