CVE-2026-43198MediumMicrosoft CVSS 4.8CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:U

Microsoft security update for CVE-2026-43198 — azl3 kernel

Published
May 22, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-43198. This page also shows what EchelonGraph holds for CVE-2026-43198, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products12

  • azl3 kernel 6.6.137.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.138.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.139.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.141.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.143.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.144.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.145.2-1 on Azure Linux 3.0
  • azl3 kernel 6.6.150.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.152.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.157.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.161.1-1 on Azure Linux 3.0

✅ Updates Microsoft lists: 1 update

1 row: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—

🧭 EchelonGraph on CVE-2026-43198

EchelonGraph score
9.8 CRITICAL
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

In the Linux kernel, the following vulnerability has been resolved: tcp: fix potential race in tcp_v6_syn_recv_sock() Code in tcp_v6_syn_recv_sock() after the call to tcp_v4_syn_recv_sock() is done too late. After tcp_v4_syn_recv_sock(), the child socket is already visible from TCP ehash table and other cpus might use it. Since newinet->pinet6 is still pointing to the listener ipv6_pinfo bad things can happen as syzbot found. Move the problematic code in tcp_v6_mapped_child_init() and call this new helper from tcp_v4_syn_recv_sock() before the ehash insertion. This allows the removal of one tcp_sync_mss(), since tcp_v4_syn_recv_sock() will call it with the correct context.

Published by kernel.org, the CVE Numbering Authority that assigned CVE-2026-43198, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)