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.

Linux's Role as CNA: Managing Kernel Security Vulnerabilities and CVE Tracking

By

voxadam

5mo ago· 3 min readenInsight

Summary

The article discusses Linux's transition to becoming a CNA (Certificate Numbering Authority) for the Linux kernel, making the kernel.org community responsible for issuing all CVEs (Common Vulnerabilities and Exposures). It highlights that Linux has rapidly become one of the largest creators of CVEs by quantity, moving from nothing to number 3 in 2024 and number 1 in 2025. The article addresses questions about how this work is being managed and how people can track the increasing volume of security vulnerabilities being documented.

Key quotes

· 3 pulled
It's been almost 2 full years since Linux became a CNA (Certificate Numbering Authority) which meant that we (i.e. the kernel.org community) are now responsible for issuing all CVEs for the Linux kernel.
During this time, we've become one of the largest creators of CVEs by quantity, going from nothing to number 3 in 2024 to number 1 in 2025.
Naturally, this has caused some questions about how we are both doing all of this work, and how people can keep track of it.
Snippet from the RSS feed
It’s been almost 2 full years since Linux became a CNA (Certificate Numbering Authority) which meant that we (i.e. the kernel.org community) are now responsible for issuing all CVEs for the Linux kernel. During this time, we’ve become one of t

You might also wanna read