An installed kernel update helps only after the host boots it. For Azure Linux 4.0 systems using networked storage, start by identifying which hosts initiate iSCSI sessions or serve NFSv4.

What I verified on November 22
On November 22, 2026, I verified that Microsoft’s production base repositories carry 0:6.18.62-1.1.azl4 for x86-64 and ARM64. Microsoft’s November 20 UTC advisory data lists 6.18.57-1.12.azl4 as affected for the three issues below and maps it to that fixed release. The repository files were already hosted November 19 UTC. Both repository metadata checksums matched, and Microsoft’s download endpoints returned HTTP 200 for the matching kernel, core, modules and virtual UKI packages. Earlier Azure Linux package bounds and customer deployment status remain unverified.
Which hosts to prioritize
CVE-2026-99153 and CVE-2026-99154 affect Linux iSCSI initiators that use the vulnerable libiscsi path and receive responses from a malicious or compromised storage target. The second issue also requires a transport that uses the affected task-index handling. Microsoft rates both Critical, CVSS 3.1 9.8. The Linux CNA published both October 28 and lists upstream 6.18.59 as fixed on the 6.18 branch.
CVE-2026-99310 is a use-after-free in the kernel NFS server’s NFSv4 client-state handling. Check hosts with the affected NFSv4 server path enabled and reachable by untrusted clients. Microsoft publishes CVSS 3.1 9.8 and leaves the Azure Linux 4.0 severity label blank in the reviewed row. The Linux CNA published this issue November 16 and lists upstream 6.18.61 as fixed on the 6.18 branch.
CISA KEV lists none of these three CVEs as of November 22. The reviewed official sources did not establish confirmed exploitation, a federal KEV deadline, a vendor workaround or a new incident-response requirement. Microsoft’s package mapping addresses the listed Azure Linux 4.0 build. Check AKS images, cloud appliances and other distributions through their own supported update paths.
Suggested MSP priority is High for affected storage hosts with NFSv4 reachability from untrusted networks or iSCSI sessions to storage that crosses a trust boundary.
What to check before and after rollout
- Inventory the running kernel, architecture, image type, active iSCSI targets, transports and NFSv4 listening interfaces or exports.
- If patching must wait, restrict storage access to required clients and approved targets where feasible. Check multipath, boot-from-storage dependencies and service impact before changing reachability.
- Pilot the matched Microsoft production update and reboot affected hosts under the normal maintenance procedure. Verify the booted kernel, multipath, iSCSI sessions, NFS mounts and application I/O.
- Track container hosts and managed node pools using their actual host or node image, and verify workload recovery after rollout.
Official sources
Last verified November 22, 2026 ET. Microsoft October CVRF · Microsoft November CVRF · Linux CNA CVE-2026-99153 · Linux CNA CVE-2026-99154 · Linux CNA CVE-2026-99310 · Microsoft x86-64 base repository · Microsoft ARM64 base repository · CISA KEV.