Linux is a ravishing factor. From a very open-source base, we’ve got in all probability ten quintillion totally different distros that deal with us like adults, able to really proudly owning, controlling, and tinkering with our software program. Together with, in fact, current boons for gaming akin to SteamOS, Bazzite, and Nobara. However that exact same free and open basis may also deliver with it some hurdles, akin to longstanding bugs.
Researcher and developer Jenny Guanni Qu just lately appeared on the Linux kernel’s bug fixes and located tons of them stick round for a really very long time. As somebody who feels the attract of Linux distributions and sometimes succumbs to it earlier than rapidly scarpering again to Home windows when confronted with bugs—normally small and irksome ones, however sometimes catastrophic—this data doesn’t assist me. So if you happen to’re the identical as me: you are welcome.
As an alternative, if we examine the stats that truly matter and make sense, we’re enhancing: “We’re concurrently catching new bugs quicker AND slowly working via ~5,400 historical bugs which have been hiding for over 5 years.”
It is not all the identical throughout the board, in fact: some sorts of bugs are mounted quicker than others. Networking bugs are likely to take longer, and GPU bugs are faster. There are additionally sure sorts of bugs that take for much longer than others to identify and repair, however that are to be anticipated, for example “race-condition” ones which can be “non-deterministic and solely set off beneath particular timing circumstances which may happen as soon as per million executions.”
CES 2026
Meet up with CES 2026: We’re on the bottom in sunny Las Vegas masking all the most recent bulletins from among the largest names in tech, together with Nvidia, AMD, Intel, Asus, Razer, MSI and extra.
Normally, the much less a bug is triggered and the less eyes reviewing its codebase, the longer it’s going to take to be noticed and glued. Burrowing in additional particularly, for anybody , these longstanding bugs are likely to contain a couple of causes: “reference counting errors”, “lacking NULL checks after dereference”, “integer overflow in dimension calculations”, and “race circumstances in state machines.”
Actually, although, zooming out once more, they’re typically simply bugs that function beneath fairly uncommon circumstances. Qu provides an instance of one of many oldest networking bugs they noticed, which spent 19 years unfixed. That caught round for therefore lengthy as a result of it solely occurred when operating a particular check sequence for a particular size of time, and “no one ran that particular check sequence for 20 years.”
All of that is introduced as a cause to contemplate the researcher’s VulnBERT AI mannequin, “a mannequin that predicts whether or not a commit introduces a vulnerability.” Apparently, “of all precise bug-introducing commits, we catch 92.2%.”
Which will likely be nice for these checking via Linux kernel git commits, in fact. However for me, as a plain ol’ end-user—and on the fully unintentional danger of annoying our Linux readers who will undoubtedly level out simply how unhealthy Home windows is for bugs—it is simply extra gas to my Linux trepidation.

Greatest PC gaming equipment 2026
