Canonical, the company behind the Ubuntu operating system, has announced a major shift in its update model. Previously, Ubuntu followed a 4/2 schedule, where maintenance updates were released every four weeks and security updates every two weeks. Now, Canonical is moving to a unified 2-week update cycle, which overlaps and results in the release of a new Ubuntu kernel every week. This change comes in response to a growing number of vulnerabilities, known as CVEs (Common Vulnerabilities and Exposures), being automatically identified by artificial intelligence tools working on Linux systems. These discoveries have forced software publishers to rethink their approaches to security. The new update approach includes a rapid 2-week Stable Release Update (SRU) cycle, where each release still undergoes extensive testing to maintain the reliability and quality that Ubuntu users expect. However, this change has sparked debate. Some critics compare it to the update model used by Windows 11, which has faced user complaints about its update management. The number of CVEs per Linux kernel version is now approaching 2,000, partly because the Linux kernel community has taken on the role of its own CVE numbering authority (CNA). This means that almost any bug, even minor ones, can be assigned a CVE if it could potentially be exploited. Some argue this leads to unnecessary fixes and more frequent updates. The new strategy offers benefits, such as a significant reduction in the time that known security flaws remain unpatched. The weekly release pace allows for quicker deployment of fixes. Each kernel version is prepared over two full weeks: the first for integrating patches and initial testing, and the second for regression testing and hardware certification. Teams needing urgent fixes can access early versions through the -proposed repository. However, the increased update frequency presents challenges. For administrators managing large server fleets or machine parks, the weekly update pace has become a critical constraint, increasing the risk of introducing system issues in production. Automating reboots and validating server clusters has become more important, as updating a Linux kernel typically requires rebooting the system. Additionally, the increased update frequency places more pressure on internal validation processes, with companies needing to decide whether to trust Canonical's certification or build their own automated testing environments. This shift is not unique to Canonical. The entire software industry is moving toward AI-assisted development and auditing. Microsoft and Google have also seen a rise in the frequency of out-of-schedule fix waves. Microsoft released 620 fixes in a single week, while Google published 433 fixes for Chrome. Even the cURL project closed its public Bug Bounty program due to an influx of AI-generated reports that described fictional or out-of-context security flaws.