All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Analysis of Human Factors in 125,000 Linux Kernel Vulnerabilities: Who Writes Bugs and When

By

MBCook

2mo ago· 17 min readenInsight

Summary

This article analyzes 125,000 Linux kernel vulnerabilities to understand the human factors behind bug introduction. It examines who writes buggy code, when vulnerabilities are introduced, and identifies super-reviewers who catch bugs. The analysis reveals that most vulnerabilities are introduced by experienced developers, not newcomers, and that bugs are more likely to be introduced during certain times (like late-night coding). The article also discusses practical interventions to reduce vulnerability introduction rates.

Key quotes

· 4 pulled
This time I asked different questions: Who writes the buggy code? When do they write it? And who are the super-reviewers who catch bugs
I analyzed 125,000 kernel bugs and found they hide for 2.1 years on average, with race conditions surviving over twice as long as other bug types
But that analysis treated bugs as abstract data points
This post digs into the human side: who introduces vulnerabilities, when they do it, and what we can do about it
Snippet from the RSS feed
Part 2 of our kernel vulnerability analysis. Part 1 covered bug lifetimes and VulnBERT. This post digs into the human side: who introduces vulnerabilities, when they do it, and what we can do about it.

You might also wanna read