A simultaneous rollout of three .NET versions across three enterprise Linux generations shows how vendors balance long term support against staying current.
LWN's Thursday security-updates digest is usually a reference page rather than a story: a curated table of advisories that landed across the major Linux distributions. The 2026-06-11 edition is a useful test of that rule, because underneath the list sits a real pattern. On the same day, Red Hat and AlmaLinux pushed .NET 8.0, 9.0, and 10.0 across Enterprise Linux. EL 8 and EL 10 received all three majors; EL 9 received .NET 8.0 and 10.0 only. Shipping three major versions of a runtime in one coordinated wave is a maintenance story, not a vulnerability story, and the digest makes that pattern visible only because the per-distro advisories are listed side by side.
The LWN roundup records AlmaLinux's .NET 8.0, 9.0, and 10.0 advisories landing on 2026-06-11 (Security updates for Thursday). Red Hat's advisory IDs from the same digest include RHSA-2026:25110-01 (EL8 .NET 8.0), RHSA-2026:25111-01 (EL10 .NET 8.0), RHSA-2026:25220-01 (EL9 .NET 8.0), RHSA-2026:25113-01 (EL8 .NET 9.0), RHSA-2026:25112-01 (EL10 .NET 9.0), RHSA-2026:25114-01 (EL8 .NET 10.0), RHSA-2026:25115-01 (EL10 .NET 10.0), and RHSA-2026:25222-01 (EL9 .NET 10.0) (Security updates for Thursday). EL 8 and EL 10 each received .NET 8.0, 9.0, and 10.0 on the same Thursday; EL 9 received .NET 8.0 and 10.0 only, with no .NET 9.0 advisory appearing for that distribution.
That partial-parity maintenance is not free. It means the vendor is maintaining build pipelines, ABI tests, and security-errata workflows for a current release alongside at least one prior long-term-support release, and shipping them with synchronized dates so downstream consumers can plan. The cost of doing this well is the cost of the L in LTS: extra test infrastructure, extra patch backports, and a deliberate refusal to declare any of the three majors finished just because a newer one shipped. Enterprise distributions earn their support contracts on exactly that discipline, and the visible artifact is the day the advisories land.
The other items in the digest belong in subordinate context, because none of them shows the same cross-version shape. Oracle published a pair of kernel advisories on 2026-06-10 (ELSA-2026-50305 and ELSA-2026-50306) for OL 8 and OL 7. Debian's 2026-06-10 wave included DSA-6337-1 (chromium) and DSA-6336-1 (jackson-core), with libinput (DSA-6339-1) and libdbi-perl (DSA-6338-1) following on 2026-06-11. Mageia's MGASA-2026-0192 (postfix) and MGASA-2026-0194 (roundcubemail) cover mail infrastructure across 2026-06-10 and 2026-06-11, and Fedora's FEDORA-2026 advisory for httpd on F44 lands on 2026-06-11. None of those rows argues for a different story on its own, and listing them in parallel with the .NET thread would be exactly the "big patch day" framing the digest's own structure does not support.
The thread worth watching is whether the .NET pattern holds into the next monthly cadence. If RHEL 8 and 9 keep receiving the 8.0 and 9.0 streams on the same day that RHEL 10 receives 10.0 — and if EL 9 eventually receives .NET 9.0 — that would signal a more complete parity posture. If one of the streams slips or EL 9 remains on only two majors, that is also a story: it would tell readers which major is closest to the end of its support ride.