Linux 7.3 is expected to be designated the Long Term Support kernel for 2026, positioning it as the tree that enterprise distributions, cloud providers and embedded vendors will build their multi-year support matrices around — with formal confirmation still pending upstream.
Phoronix reported on 4 November that the likely designation is 7.3, while Linux 7.4 remains on track to ship in the last week or two of December 2026 if the merge-window and release schedule holds. The LTS label, however, is expected to land on 7.3 rather than the year's final release.
LTS status explained
The distinction matters more than it might first appear. LTS status is a maintenance-policy decision, not a schedule signal: it determines which kernel branch receives years of stable-tree updates and security fixes, not when releases ship. Nothing in the reporting suggests a delay to 7.4 or any shift in the upstream release cadence, and readers should not infer one.
For infrastructure teams, the LTS choice is arguably the highest-leverage detail in a year-long roadmap. It defines the baseline around which downstream distributions align their kernels, which hardware platforms get long-lived driver support, and which versions remain inside vendor support contracts.
Timing reinforces the point. A late-December 7.4 release would land after most year-end change freezes, and a support clock starting that late would be awkward to anchor to a product line intended to run for several years. This matters because it separates two questions that are easy to conflate: 7.4's position as the year's final release, and which tree carries the LTS commitment. On the current schedule, those answers are not the same.
Planning implications
DevOps and IT managers planning kernel platforms for 2027 and beyond should treat 7.3 as the likely long-lived target while confirmation remains outstanding:
- Anchor long-lived builds to 7.3. Base production images, appliance firmware and certified hardware profiles on the 7.3 line, where multi-year stable updates are expected to concentrate.
- Treat 7.4 as an early-adopter track. Evaluate it in staging for access to the newest features, but avoid committing it to anything requiring a long support horizon.
- Align hardware qualification with the 7.3 cycle. Driver enablement and device certification efforts scheduled for the next two years should target 7.3 first; 7.4 can follow once downstream distributions carry it.
Procurement deserves the same scrutiny as engineering. When reviewing distribution support terms, cloud instance commitments or hardware support contracts, confirm explicitly which kernel branch the vendor's guarantee covers rather than assuming the LTS label carries through.
Caveats and what to watch
The designation as reported remains likely rather than confirmed. LTS windows also rest on the continuing work of volunteer and corporate maintainers, and the length of support upstream grants to a given release has not been uniform across history. Teams committing to a multi-year horizon should therefore watch the Linux kernel mailing list and stable-tree announcements for formal confirmation — and for any variation from the window set for 7.3 — before locking contracts or certification schedules.
A follow-up check on those announcements before publication of any 2027 roadmap would be prudent, since an unexpected support-window change would alter the cost calculus of standardising on 7.3 versus waiting for a later release.
Linux 7.3 預料將獲指定為 2026 年的長期支援（Long Term Support）kernel，使其成為企業級發行版、雲端服務供應商及嵌入式廠商據以構建多年支援架構的版本分支——惟上游方面尚未正式確認。
Phoronix 於 11 月 4 日報道，最有可能獲指定的版本為 7.3，而 Linux 7.4 若 merge window 及發布時間表維持不變，仍有望於 2026 年 12 月最後一兩週發布。不過，LTS 標籤預料將落在 7.3，而非該年度的最後一個版本。
LTS 身分詳解
這項區別的重要性，較表面看來更大。LTS 身分屬一項維護政策決定，並非發布節奏的指標：它決定哪一條 kernel 分支可獲多年 stable tree 更新及安全性修復，而非版本何時發布。報道中並無任何內容顯示 7.4 會延誤，或上游發布節奏會有所改變，讀者不應從中作此推斷。
對基建團隊而言，LTS 的選擇可說是一整年路線圖中最具影響力的細節。它訂立了下游發行版對齊其 kernel 的基準、決定哪些硬件平台可獲長期驅動支援，以及哪些版本仍處於廠商支援合約範圍之內。
時機問題進一步強化了這一點。若 7.4 於 12 月下旬發布，將落在大多數年終變更凍結期之後，而支援時鐘若如此遲才啟動，要對接一條預期運行多年的產品線會相當尷尬。此舉重要之處在於，它區分了兩個容易混淆的問題：7.4 作為該年度最後一個版本的地位，以及哪一個 tree 承載 LTS 承諾。按照現行時間表，這兩個問題的答案並不相同。
規劃影響
為 2027 年及以後規劃 kernel 平台的 DevOps 及 IT 管理人員，在正式確認仍然懸而未決之際，應將 7.3 視為最可能的長期目標：
- 將長期構建錨定於 7.3。 以 7.3 分支為基礎構建 production image、裝置韌體及認證硬件配置，預期多年 stable 更新將集中於此分支。
- 將 7.4 視為早期採用者軌道。 可在 staging 環境中評估 7.4，以接觸最新功能，但避免將其部署於任何需要長遠支援時限的用途。
- 將硬件認證與 7.3 周期對齊。 未來兩年計劃進行的驅動啟用及設備認證工作，應優先以 7.3 為目標；7.4 可待下游發行版採納後再跟進。
採購流程應獲得與工程環節同等的審視。在檢視發行版支援條款、雲端實例承諾或硬件支援合約時，應明確確認廠商保證涵蓋哪一條 kernel 分支，而非想當然假設 LTS 標籤會自然延伸適用。
注意事項及關注重點
根據報道，該指定仍然只是「很可能」，尚未確認。LTS 窗口亦由義工及企業維護者的持續工作所支撐，上游對特定版本給予的支援時長在歷史上並非一致。因此，承諾多年時間表的團隊應留意 Linux kernel mailing list 及 stable tree 公告，等待正式確認——以及任何偏離 7.3 所設窗口的變化——然後才鎖定合約或認證時間表。
在發布任何 2027 年路線圖之前，先覆核相關公告屬審慎做法，因為支援窗口一旦意外變動，將會改變在 7.3 上標準化與等待較後版本之間的成本衡量。