Microsoft Azure Linux 4 ships with post-quantum OpenSSL 3.5
Microsoft releases Azure Linux 4 on the Linux 6.18 LTS kernel with enforcing SELinux by default, signed driver validation, and post-quantum OpenSSL 3.5.

The general availability of Microsoft Azure Linux 4 redefines the baseline for cryptographic security and process isolation across Kubernetes clusters and cloud-native workloads. Built upon the Linux 6.18 LTS kernel, this fourth generation of Microsoft's in-house Linux distribution for Azure Kubernetes Service (AKS) and hybrid deployments on Azure Local introduces three structural defense pillars: native integration of OpenSSL 3.5 featuring NIST-standardized post-quantum algorithms, default enforcement of SELinux in enforcing mode, and strict cryptographic verification of all loadable kernel drivers.
For years, container-optimized operating system images prioritized fast boot times and broad package compatibility over strict control-plane isolation, frequently leaving mandatory access control frameworks in permissive mode or disabled entirely to avoid operational friction. However, the surge in intrusion campaigns targeting container-to-hypervisor escapes and the regulatory urgency to protect inter-service TLS traffic against passive quantum interception prompted Microsoft's systems engineering team to harden every layer of the OS from the hardware root of trust up to user-space cryptographic libraries.
Linux 6.18 LTS kernel architecture and ring-zero cryptographic lockdown
At the core of Azure Linux 4 sits the Linux 6.18 LTS kernel, preconfigured with kernel lockdown policies in integrity and confidentiality modes whenever running on instances with UEFI Secure Boot enabled. One of the most heavily exploited persistence vectors across enterprise infrastructure in recent years is the Bring Your Own Vulnerable Driver (BYOVD) attack, where an adversary who has gained superuser (root) privileges on a node loads a legitimate but outdated kernel module containing known memory corruption flaws—or an ad-hoc compiled malicious module—to blind EDR telemetry agents and tamper with internal kernel structures.
Azure Linux 4 eliminates this attack surface by enforcing CONFIG_MODULE_SIG_FORCE and CONFIG_SECURITY_LOCKDOWN_LSM inside the 6.18 LTS kernel. Under this architecture, the kernel module loader immediately rejects any .ko binary lacking a cryptographic signature generated by Microsoft Azure Linux build keys, whose corresponding public certificate is anchored in the kernel's immutable keyring (.builtin_trusted_keys) and chained to the node's TPM 2.0 platform configuration registers. Even a privileged process holding the CAP_SYS_MODULE capability and root permissions receives an immediate key rejection error (EKEYREJECTED) if it attempts to insert an unauthorized external driver.
Furthermore, the Linux 6.18 LTS memory subsystem in Azure Linux 4 incorporates forward-edge Control Flow Integrity protections (FineIBT on modern x86_64 processors and PAC/BTI on ARM64 Cobalt architectures), paired with per-syscall kernel stack layout randomization (CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT=y). Before deploying custom node images into production environments, security engineers can verify the checksums of VHDX or ISO artifacts using a cryptographic hash generator and align their release pipeline with formal SHA-256 file integrity verification standards.
Native OpenSSL 3.5 and the post-quantum transition in mTLS service meshes
Integrating OpenSSL 3.5 as the primary system cryptographic library makes Azure Linux 4 one of the first enterprise cloud distributions to deliver native post-quantum cryptography without relying on experimental patches or third-party loadable modules such as oqs-provider. In earlier OpenSSL 3.x releases, organizations seeking to deploy lattice-based algorithms across Envoy reverse proxies, NGINX ingress gateways, or service meshes had to compile and dynamically load external providers, complicating compliance audits and increasing per-container memory overhead.
With OpenSSL 3.5, both the default provider and the validated fips provider include native, assembly-optimized implementations for all three post-quantum standard families published by NIST:
- ML-KEM key encapsulation (FIPS 203): direct TLS 1.3 protocol support for standalone post-quantum key exchange groups (
MLKEM512,MLKEM768,MLKEM1024) as well as IETF-standardized hybrid groups includingX25519MLKEM768andSecP256r1MLKEM768. - ML-DSA lattice-based digital signatures (FIPS 204): key-pair generation, Certificate Signing Request (CSR) creation, and X.509v3 certificate chain validation across
ML-DSA-44,ML-DSA-65, andML-DSA-87security parameter sets. - SLH-DSA stateless hash-based signatures (FIPS 205): support for both fast (
f) and small (s) variants using SHA-2 and SHAKE primitives to sign container manifests, long-lived firmware binaries, and internal Certificate Authority root certificates.
Adopting hybrid key exchange schemes such as X25519MLKEM768 across Kubernetes service meshes ensures that internal mTLS traffic between financial or healthcare microservices remains immune to passive quantum harvesting without sacrificing handshake throughput.
For platform engineering teams managing distributed cloud environments and tracking the deployment of post-quantum algorithms in enterprise networks, this native OpenSSL 3.5 integration means any application dynamically linked against libssl.so.3 and libcrypto.so.3 on Azure Linux 4 automatically inherits the ability to negotiate post-quantum TLS 1.3 simply by updating the Groups directive inside /etc/pki/tls/openssl.cnf. External verification of exposed ingress endpoints can also be performed using an SSL certificate inspector to audit public certificate chains.
| Architectural feature | Azure Linux 3.0 (Legacy CBL-Mariner) | Microsoft Azure Linux 4.0 | Cloud security impact |
|---|---|---|---|
| Base kernel version | Linux 6.6 LTS | Linux 6.18 LTS with ring-zero lockdown | Memory corruption mitigation and strict cgroups v2 resource isolation |
| TLS cryptographic engine | OpenSSL 3.3 (required external provider for PQC) | OpenSSL 3.5 with native ML-KEM, ML-DSA, and SLH-DSA | Default hybrid mTLS protection against passive quantum harvesting |
| Mandatory access control | SELinux available but permissive in several profiles | SELinux in enforcing mode by default on host and AKS |
Container escape prevention and strict system daemon confinement |
| Kernel module policy | Optional verification depending on deployment profile | Mandatory cryptographic signing + BYOVD prevention | Inability to load rootkits or vulnerable drivers into ring zero |
Enforcing SELinux by default for containerized workloads
The third foundational shift in Azure Linux 4 is mandating SELinux in enforcing mode as the default operational state across all deployment images for bare-metal servers, virtual machines, and AKS worker nodes. Historically, many cluster operators disabled SELinux on container hosts due to Access Vector Cache (AVC) labeling denials when mounting persistent volumes across pods or running monitoring agents that needed to inspect the host /proc filesystem.
Microsoft re-engineered the base SELinux policy in Azure Linux 4 in close coordination with the containerd runtime and the container-selinux policy module. Every unprivileged container spawned on a node is automatically assigned the container_t domain type along with a unique, randomly generated Multi-Category Security (MCS) label (for example, s0:c124,c589). Even if a process inside a container runs as UID 0 (root) and exploits a logical flaw in the container runtime to reach a file descriptor belonging to another pod or the underlying host system (spc_t / unconfined_service_t), the Linux 6.18 LTS security hook intercepts the syscall and blocks the operation because the MCS category labels do not match.
Verification commands and post-quantum configuration on Azure Linux 4
The following command block demonstrates how to inspect an Azure Linux 4 node's SELinux enforcement status, verify the post-quantum algorithms natively registered in OpenSSL 3.5, generate an X.509 certificate signed with ML-DSA-65, and confirm kernel module lockdown:
sestatus
cat /sys/kernel/security/lockdown
# Expected output: none [integrity] confidentiality
# 2. Check native ML-KEM and ML-DSA support in OpenSSL 3.5 default provider
openssl list -kem-algorithms | grep -E "ML-KEM|X25519MLKEM768"
openssl list -signature-algorithms | grep -E "ML-DSA|SLH-DSA"
# 3. Generate a private key and self-signed X.509 certificate using ML-DSA-65 post-quantum signature
openssl genpkey -algorithm ML-DSA-65 -out /etc/pki/tls/private/service-mldsa65.key
openssl req -new -x509 -key /etc/pki/tls/private/service-mldsa65.key \
-out /etc/pki/tls/certs/service-mldsa65.crt -days 365 \
-subj "/CN=internal-api.aks.corp.internal/O=Cloud Security"
# 4. Enable the hybrid X25519MLKEM768 group by default in TLS 1.3 system-wide
cat << 'EOF' | sudo tee -a /etc/pki/tls/openssl.cnf
[system_default_sect]
MinProtocol = TLSv1.3
Groups = X25519MLKEM768:SecP256r1MLKEM768:x25519:secp384r1
EOF
# 5. Audit SELinux AVC denials across containers without disabling enforcing mode
sudo ausearch -m AVC,USER_AVC -ts recent
This configuration ensures that both workload identity certificates issued inside the cluster and TLS 1.3 sessions initiated by operating system clients default to the hybrid X25519MLKEM768 key exchange group while maintaining transparent backward compatibility with external endpoints that only support x25519 or secp384r1.
A new hardening standard for cloud-native infrastructure
With the release of Azure Linux 4, Microsoft establishes a security baseline where post-quantum cryptography, mandatory access control, and cryptographic kernel integrity are no longer optional post-deployment add-ons. By combining the resilience of the Linux 6.18 LTS kernel against malicious driver injection, granular MCS category confinement under enforcing SELinux, and the native performance of OpenSSL 3.5 for executing FIPS 203, 204, and 205 standards, organizations gain a purpose-built operating system engineered to withstand both modern privilege escalation techniques and the cryptanalytic threats of the coming decade.


