Incorrect Synchronization Affecting kernel-livepatch-6.18.16-18.222 package, versions <1:1.0-0.amzn2023


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.05% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-KERNELLIVEPATCH6181618222-16740468
  • published18 May 2026
  • disclosed6 May 2026

Introduced: 6 May 2026

NewCVE-2026-43198  (opens in a new tab)
CWE-821  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-livepatch-6.18.16-18.222 to version 1:1.0-0.amzn2023 or higher.
This issue was patched in ALAS2023-2026-1711.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6.18.16-18.222 package and not the kernel-livepatch-6.18.16-18.222 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1