{"id":183458,"date":"2026-09-25T04:54:13","date_gmt":"2026-09-25T02:54:14","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/ubuntu-perehodit-na-uskorennyj-czikl-ustraneniya-uyazvimostej-v-paketah-s-yadrom-linux"},"modified":"2026-09-25T04:54:19","modified_gmt":"2026-09-25T02:54:19","slug":"ubuntu-moves-to-a-faster-vulnerability-fix-cycle-for-linux-kernel-packages","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/ubuntu-moves-to-a-faster-vulnerability-fix-cycle-for-linux-kernel-packages","title":{"rendered":"Ubuntu moves to an accelerated vulnerability patch cycle for packages with the Linux kernel","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Canonical has announced a transition to a unified two-week preparation cycle for Linux kernel package updates, with a new update being released each week. The update development cycle has been shortened due to the increasing intensity of vulnerability discovery in the Linux kernel. The new cycle for generating the next corrective package update will now kick off every week without distinguishing between regular updates and security fixes. <\/p>\n
The deployment of each update addressing vulnerabilities will take two weeks \u2014 one week for preparation, assembly, and basic testing of the package, and the second week for extensive testing, regression detection, and certification. Thus, new versions of the packages with the kernel will now be published every week, and the maximum delay in addressing critical vulnerabilities will not exceed two weeks.
<\/center> <\/p>\n
For users who wish to apply vulnerability patches as soon as possible and are ready to use a package that has not passed all testing phases, preliminary updates will be available in the 'proposed' repository one week earlier. Additionally, within 24-48 hours after public disclosure of a vulnerability, Canonical will publish possible workarounds to block the vulnerability, and if no workarounds are available, recommend general protective measures. <\/p>\n
Previously, a combined scheme was employed where a regular update of kernel packages was published once every four weeks, and two weeks after the start of the formation cycle of the next regular update, a separate update was released that included fixes only for critical vulnerabilities and important issues. Preparation and testing of regular updates before publication took four weeks, while intermediate updates addressing vulnerabilities took two weeks. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![](\"\/wp-content\/uploads\/2026\/09\/13f78027d9155880989ab7d1432e736f.jpg\")
<\/center> <\/p>\n