Linux kernel maintainers have accelerated the decommissioning of legacy hardware drivers within the networking subsystem as of April 22, 2026. This strategic shift follows a sustained increase in the volume of security vulnerability reports generated by large language models (LLMs). These automated reports, which often identify theoretical memory safety issues or potential buffer overflows in aging codebases, have created a significant administrative bottleneck for the core development team during the Linux 6.14 kernel development cycle.
Jakub Kicinski, a lead maintainer for the Linux networking stack, confirmed that the decision to remove code rather than issue patches is a direct response to the low-signal nature of many LLM-driven submissions. Maintainers report that while AI tools are proficient at identifying common weakness enumerations (CWEs), the reports frequently lack context regarding whether the affected code is reachable in modern production environments. Consequently, the effort required to triage, verify, and fix these issues in unmaintained drivers has begun to outweigh the utility of keeping the drivers in the kernel.
Technical documentation released today indicates that 28 legacy drivers, representing approximately 52,000 lines of code, have been removed from the mainline kernel tree. The removals primarily target the net/ethernet and net/wireless directories, focusing on hardware that has reached end-of-life status from manufacturers. Specific drivers removed include support for several 10/100 Mbps Ethernet controllers and early 802.11b wireless adapters that have not received functional updates or active maintenance in over a decade.
The Linux kernel community has faced a growing challenge with the automation of bug hunting. While automated fuzzing and static analysis have long been part of the kernel's security posture, the accessibility of LLMs has democratized the ability to generate high-volume security reports. Maintainers have noted that many of these reports are submitted by individuals seeking to participate in bug bounty programs or bolster security credentials, often without providing the necessary hardware-specific testing required for a reliable patch. This has led to a backlog of over 1,500 pending reports specifically targeting legacy networking components.
By removing the unmaintained code, the kernel team aims to reduce the overall attack surface and streamline the maintenance of the networking subsystem. This approach is supported by senior maintainers, including Greg Kroah-Hartman, who has advocated for the removal of bit-rotting code. The move signals a stricter enforcement of the use-it-or-lose-it policy for kernel drivers, where code without an active maintainer or a verified user base is prioritized for deletion when it becomes a source of recurring security noise.