Linux has now reached 35 years old, serving as a reminder of the modern world’s reliance on an open-source kernel. On August 25, 1991, a 21-year-old student at the University of Helsinki, Linus Torvalds, announced his work on the comp.os newsgroup.minix Usenet group.
He introduced a free operating system for 386/486 AT clones that he described as “just a hobby” and not something “big and professional like GNU.”
Linux Turns 35
The project had been in development since April, according to Torvalds. The first public release followed in September. Initially, he considered naming it “Freax,” a blend of free, freak, and Unix, as reported by CSN.
However, when a colleague uploaded the first public tree, they used the name “Linux” for the directory, which ultimately became the chosen name.
From that modest beginning, the kernel has evolved into shared infrastructure. Linux.com states that the project started with around 10,000 lines of code; today, the source tree exceeds 40 million lines, growing by approximately 400,000 lines every two months.
This vast scale results from a development model in which hundreds of maintainers and thousands of contributors, not just one vendor, review and advance the code.
The operational impact of Linux is equally significant. It runs much of the internet and public cloud, powers Android devices, and is crucial for high-performance computing.
Its role extends to systems whose availability has national and economic implications, including cloud control planes, carrier platforms, research clusters, enterprise servers, and embedded equipment.
For security teams, this widespread usage changes the implications of a kernel vulnerability. A local privilege-escalation flaw, a network-facing bug, or a vulnerable driver may start as an upstream issue but can propagate through various distributions, long-term support branches, appliances, cloud images, and device vendors.
Therefore, asset inventory, timely patching, backporting, and exposure assessment are as critical as the upstream CVE description.
The risks associated with these vulnerabilities were starkly highlighted by the Copy Fail incident in 2026. Tracked as CVE-2026-31431, this actively exploited local privilege-escalation flaw allowed unprivileged users to gain root access on vulnerable systems, affecting mainstream distributions that shipped susceptible kernels.
The open development process is both a strength and a point of pressure. Public code reviews, disclosures, regression testing, and stable backports allow for extensive scrutiny, but the expanding codebase also offers researchers and attackers more complex interfaces to examine. In response, maintainers are increasingly using memory-safe Rust for suitable new kernel components.
This transition has progressed beyond the experimental stage. At the 2025 Kernel Maintainers Summit, developers reached an agreement that Rust in the kernel was no longer experimental and had become a core, permanent part of the project.
Consequently, Linux 7.0 removed Rust’s experimental status, making the language a supported option alongside C for kernel development.
Thus, this anniversary is not merely a celebration of longevity. Linux continues to evolve as a crucial dependency with a vast trust boundary. Its next 35 years will depend on whether the community can maintain the pace of review, hardening, and patch delivery required by infrastructure that increasingly cannot afford to fail.
Prevent incidents due to slow investigations. Power your Tier 1 with threat intelligence from 15K SOCs: Integrate TI Lookup in your SOC
