A seemingly technical update to the Linux kernel in April 2026 sparked a significant amount of discussion within the global technology community. The decision to start the process of removing support for Russia’s Baikal processors from the Linux kernel was not just another routine cleanup of outdated code. Rather, it was indicative of a deeper interplay of sanctions, geopolitics, open-source governance, and the realities of hardware development in a world that is becoming increasingly polarized.
Linus Torvalds, creator of Linux and leader of a major open-source initiative, is at the center of this development. The removal of Baikal support underscores the fact that even decentralized systems are susceptible to global political pressures, although Linux itself is politically neutral in principle.
The Baikal processor initiative, the role of Linux in its development, the reasons behind the termination of support, and the implications for the future of global technology ecosystems are all examined in this article.
The Baikal Dream: Russia’s Struggle for Technological Sovereignty
In 2012, Baikal Electronics, a Russian company, was established with the objective of reducing its reliance on Western technology. As part of this activity, the Baikal processor line was developed. The initiative was closely associated with national objectives of technological sovereignty, particularly in sectors such as defense, government infrastructure, and critical computing systems.
Baikal processors were developed using a combination of architectures, such as ARM and MIPS, over time. Embedded systems were the main objective of early models like the Baikal-T1, while later processors such as the Baikal-M and Baikal-S were designed for desktops and servers.
The objective was to establish a domestic alternative to processors from Intel and AMD, and to integrate them with operating systems developed in Russia, such as Astra Linux and RED OS. These systems were designed for use in government institutions, military environments, and state-owned enterprises.
Nevertheless, the development of Baikal was significantly influenced by global supply chains. The processors were produced by Taiwan’s TSMC and incorporated intellectual property from Western companies, including ARM. This dependence would ultimately prove fatal.
The Tipping Point: Sanctions and Collapse
The turning point occurred in 2022 as a result of Russia’s invasion of Ukraine. Western nations responded by implementing extensive sanctions that targeted Russia’s technology sector. Baikal Electronics was effectively isolated from its primary suppliers and manufacturing partners as a result of its inclusion in these sanctions lists.
The repercussions were dire and immediate. ARM licensing agreements were disrupted, access to TSMC manufacturing was lost, and previously produced chips were purportedly left stranded abroad. Baikal Electronics had initiated bankruptcy proceedings by 2023.
Despite efforts to resurrect the project through the use of alternative architectures such as RISC-V, the harm had already been done. The ecosystem surrounding Baikal hardware never achieved maturity, and production volumes remained low.
A Symbiotic Relationship Between Baikal and Linux
From the very outset, Linux was essential to the Baikal ecosystem. Linux, an open-source operating system, offered a platform that was both adaptable and customizable, capable of accommodating new hardware architectures.
The mainline Linux kernel has been progressively integrated with patches and drivers that support Baikal processors over the years. These contributions were often generated by Russian developers who collaborated closely with Baikal Electronics.
Nevertheless, Linux necessitates an ongoing commitment to hardware platform support. Kernel maintainers are responsible for the updating of drivers, the resolution of defects, and the verification of compatibility with new kernel versions. Support rapidly becomes obsolete in the absence of active maintainers.
The Function of Linus Torvalds and Kernel Governance
Although Linus Torvalds is responsible for the Linux kernel, the maintainers who are responsible for specific subsystems and hardware support are the ones who typically make decisions. Linux is a distributed and meritocratic enterprise, rather than a centralized authority.
Several Russian kernel maintainers associated with sanctioned entities were removed from the Linux MAINTAINERS file in 2024 as a result of conformance requirements. This was a significant development.
This decision resulted in a cascading effect. The platform’s support began to stagnate as a result of the inability of key contributors to maintain Baikal-related code. The code became increasingly difficult to justify maintaining in the kernel as it became obsolete over time.
Linux 7.1: The Beginning of the End
The situation reached a critical point during the development of Linux 7.1. Kernel modifications initiated the removal of Baikal-specific drivers and device tree bindings, indicating the start of a more extensive cleanup process.
One of the earliest modifications was the removal of Baikal-related code from storage drivers. The maintainers acknowledged that upstream support for the platform “is not going to be finalized.”
The Baikal support was explicitly characterized as “stale” and unlikely to be completed in subsequent patches.
The main rationale for these modifications was technical. The code was unmaintained, the hardware was scarce, and there was no explicit roadmap for future development. The kernel would be overcomplicated without any tangible advantages if such code were to be maintained.
Political Reality or Technical Decision?
The broader context must be considered, despite the technical justification for the removal of Baikal support. The withdrawal of support is a reflection of the downstream effects of geopolitical events, which are directly linked to the decline of Baikal.
Linux developers contend that the kernel’s stability and security necessitate the removal of unmaintained code. This is a common practice in the field of open-source development.
Conversely, critics contend that the absence of maintenance is a direct result of the sanctions and constraints imposed on Russian developers. The collapse of Baikal Electronics and the removal of maintainers in 2024 resulted in an inability to provide ongoing support.
This raises significant questions regarding the impartiality of open-source initiatives in a world that is influenced by political and economic pressures.
The Current State of Baikal
Baikal has not entirely vanished, despite the setbacks. According to Russian sources, there are ongoing endeavors to create new processors, which may include those that are based on RISC-V. Nevertheless, these endeavors meet substantial obstacles, such as restricted access to sophisticated manufacturing technologies.
The ecosystem surrounding Baikal hardware remains underdeveloped, and production volumes remain modest. The number of Baikal processors used was relatively modest in comparison to global standards, even at its peak.
Existing users will be required to continue operating their systems by relying on older versions, such as Linux 6.18 LTS, due to the termination of support in subsequent Linux kernels.
Building an Independent Stack: Russia’s Broader Strategy
The Baikal narrative is a component of a broader trend in Russia’s technology strategy. Russia has been striving to establish a self-sufficient technology ecosystem in response to its growing isolation from Western markets.
This covers cloud infrastructure, software platforms, operating systems, and processors. Distributions such as RED OS and Astra Linux are being implemented in government and military systems as alternatives to Western software.
Nevertheless, the process of achieving genuine technological independence is resource-intensive and intricate. Sanctions have had a substantial impact on the semiconductor industry, which, in particular, necessitates access to sophisticated fabrication facilities, specialized equipment, and global collaboration.
Open Source and Global Collaboration Implications
The absence of Baikal support from Linux underscores a more extensive transformation in the character of open-source development. In the past, open source has been perceived as a collaborative and borderless endeavor that unites contributors from all over the globe.
Nevertheless, the Baikal case serves as a reminder that open source is not impervious to geopolitical realities. The trajectory of development can be influenced by legal compliance, sanctions, and supply chain disruptions.
Simultaneously, Linux’s openness implies that there are still alternatives. Russian developers have the option to fork the kernel, maintain their versions, or develop localized distributions that are specifically tailored to their requirements.
This duality—global collaboration and regional fragmentation—has the potential to become a defining characteristic of the future technology landscape.
In conclusion,
The removal of Baikal CPU support from the Linux kernel is not a straightforward narrative of one technology superseding another. The narrative is intricate and is influenced by economic constraints, technical considerations, and geopolitical tensions.
The decision is indicative of a dedication to the preservation of a clear and efficient codebase for Linus Torvalds and the Linux community. It poses an additional obstacle in Russia’s pursuit of technological autonomy.
Ultimately, the Baikal episode emphasizes a fundamental truth: technology does not exist in a vacuum, even in the realm of open source. It is intricately connected to the political and economic systems that influence our world.
The future of innovation in the years ahead will be determined by the balance between openness and sovereignty, which will remain a central question as the global tech ecosystem continues to evolve.