CVE-2026-43198
published 2026-05-06CVE-2026-43198: 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…
PriorityP350critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.30%
22.0th percentile
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.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fe89b2f05b854847784f91127319172945c1fadd | fe89b2f05b854847784f91127319172945c1fadd |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7178e2a8027423b2af17ab95df73a749a5b72e5b | 7178e2a8027423b2af17ab95df73a749a5b72e5b |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 858d2a4f67ff69e645a43487ef7ea7f28f06deae | 858d2a4f67ff69e645a43487ef7ea7f28f06deae |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 2.6.12.1 < 6.18.16 | 6.18.16 |
| linux | linux_kernel | >= 6.19 < 6.19.6 | 6.19.6 |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat7.0HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: tcp: fix potential race in tcp_v6_syn_recv_sock()
vendor_redhat·2026-05-06·CVSS 7.0
CVE-2026-43198 [HIGH] CWE-821 kernel: tcp: fix potential race in tcp_v6_syn_recv_sock()
kernel: tcp: fix potential race in tcp_v6_syn_recv_sock()
A flaw was found in the Linux kernel. A race condition exists in the TCP (Transmission Control Protocol) IPv6 (Internet Protocol version 6) socket handling, specifically within the tcp_v6_syn_recv_sock() function. This occurs because a child socket becomes visible in the TCP hash table before its IPv6-specific information is fully initialized. A remote attacker could potentially exploit this timing window, leading to an unstable system state or unexpected behavior, which may result in a denial of service (DoS).
Package: kernel (Red Hat Enterprise Linux 10) - Affected
Package: kernel (Red Hat Enterprise Linux 6) - Under investigation
Package: kernel (Red Hat Enterprise Linux 7) - Affected
Package: kernel-rt (Red Hat Enterprise L
GHSA
GHSA-rhcj-6wxj-r34p: 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()
ghsa_unreviewed·2026-05-06
CVE-2026-43198 GHSA-rhcj-6wxj-r34p: 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()
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-43198 kernel: tcp: fix potential race in tcp_v6_syn_recv_sock()
bugzilla·2026-05-06
CVE-2026-43198 [HIGH] CVE-2026-43198 kernel: tcp: fix potential race in tcp_v6_syn_recv_sock()
CVE-2026-43198 kernel: tcp: fix potential race in tcp_v6_syn_recv_sock()
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.
Discussion:
Upstream advisory:
https
Rapid7
Patch Tuesday - May 2026
blogs_rapid7·2026-05-13·CVSS 10.0
CVE-2026-41089 [CRITICAL] Patch Tuesday - May 2026
Microsoft is publishing 137 vulnerabilities on May 2026 Patch Tuesday . Microsoft is not aware of exploitation in the wild or public disclosure for any of these vulnerabilities. So far this month, Microsoft has provided patches to address 133 browser vulnerabilities, which are not included in the Patch Tuesday count above.
## Windows Netlogon: critical RCE
Anyone responsible for securing a domain controller should prioritize remediation of CVE-2026-41089 , which is a critical stack-based buffer overflow in Windows Netlogon with a CVSS v3 base score of 9.8. Exploitation leads to execution in the context of the Netlogon service, so that’s SYSTEM privileges on the domain controller. For most pentesters, that’s the point at which the customer report more or less writes itself. No privileges
https://git.kernel.org/stable/c/7178e2a8027423b2af17ab95df73a749a5b72e5bhttps://git.kernel.org/stable/c/858d2a4f67ff69e645a43487ef7ea7f28f06deaehttps://git.kernel.org/stable/c/fe89b2f05b854847784f91127319172945c1faddhttps://access.redhat.com/errata/RHSA-2026:30129https://access.redhat.com/errata/RHSA-2026:33215https://access.redhat.com/errata/RHSA-2026:33285https://access.redhat.com/errata/RHSA-2026:34094https://access.redhat.com/errata/RHSA-2026:34443https://access.redhat.com/errata/RHSA-2026:35863https://access.redhat.com/errata/RHSA-2026:35894https://access.redhat.com/errata/RHSA-2026:35896https://access.redhat.com/errata/RHSA-2026:35904https://access.redhat.com/errata/RHSA-2026:36073https://access.redhat.com/errata/RHSA-2026:36216https://access.redhat.com/errata/RHSA-2026:36348https://access.redhat.com/errata/RHSA-2026:36349https://access.redhat.com/errata/RHSA-2026:41236https://access.redhat.com/security/cve/CVE-2026-43198https://bugzilla.redhat.com/show_bug.cgi?id=2467228https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43198.json
2026-05-06
Published