Linux

15321 readers

216 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

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

142

Chart of Linux security vulnerabilities fixed per kernel version (media.piefed.social)

submitted 2 days ago by Ek-Hou-Van-Braai@piefed.social to c/linux@programming.dev

34 comments fedilink hide all child comments

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

[–] PotatoesFall@discuss.tchncs.de 21 points 2 days ago (1 children)

As somebody who is quite critical of AI, I will say, it is a fantastic tool for finding bugs early. I advise getting all your changes reviewed by a decent LLM before you push them. It often finds edge cases I forgot in my testing

[–] borosilicate@lemmy.dbzer0.com 2 points 1 day ago

To add to this, allium is a weirdly effective tool for finding bugs and clarifying intent despite being nothing more than a prompt that you present to a frontier model.

I’ve started using allium spec files as a replacement for handoff documents. It records what you want your program to do without any of the implementation details that might pollute an LLM’s context window.