Greg K-H: CVEs per release

https://social.kernel.org/notice/B9nU6wnmFvh5atXSG8

43 points · 6 comments · view on lemmy.world

6 Comments

jaybone@lemmy.zip · 17 pts · 2d (4 replies)

Using LLMs to scan code finds more bugs now.

Cyber@feddit.uk · 6 pts · 2d (3 replies)

And at the rate they're finding the bugs, they'll all be found by the end of the year.

Then no more bugs and all the LLMs can be shutdown.

InnerScientist@lemmy.world · 7 pts · 2d

I see you're a project manager. Have you considered running the ai at 1200% for one month instead?

Mondez@lemdro.id · 6 pts · 2d (1 reply)

There is a real risk that will become the attitude though, no need for security researchers, the LLMs got us covered. Great if true but it's probably not.

Cyber@feddit.uk · 3 pts · 2d

TBH, I think everyone's playing with the new thing and a bunch of people will just move on to the next big thing (augmented 3d post-realism AI?)

Then, it'll settle down into decent workflows and become more organised... it'll just be painful until that happens.

Sims@lemmy.ml · 9 pts · 2d

I had a blindspot and didn't really knew what CVE's was. Digging a little:

https://docs.kernel.org/process/cve.html "Common Vulnerabilities and Exposure (CVE®) numbers were developed as an unambiguous way to identify, define, and catalog publicly disclosed security vulnerabilities.

This article talks about op's chart specifically: https://www.howtouselinux.com/post/why-linux-kernel-cves-are-exploding-from-500-to-nearly-2000-per-release