Answer in brief
CVE-2026-43198 records a Critical severity (CVSS 9.8) vulnerability in tcp: fix potential race in tcp_v6_syn_recv_sock(). The current sources do not mark it as known exploited. The current feed maps Red Hat/kernel-rt (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/kernel-rt (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:2.6.12:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:2.6.12:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:2.6.12:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:2.6.12:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:2.6.12:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/kernel-rtgeneric | * | Not reported |
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fe89b2f05b854847784f91127319172945c1fadd || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7178e2a8027423b2af17ab95df73a749a5b72e5b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <858d2a4f67ff69e645a43487ef7ea7f28f06deae | fe89b2f05b854847784f91127319172945c1fadd, 7178e2a8027423b2af17ab95df73a749a5b72e5b, 858d2a4f67ff69e645a43487ef7ea7f28f06deae |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aef4a9ae95d1bc4f7897065011e6261026719aeb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dad1fe7db6c6519138430ac8f5e589c18f83bfc9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a7e761ba55efaa9c49e0afdd304bb78167af3429 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cd644e6dc72eec8d9d988717ea1c54f8668ded69 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9ed654e340f4c73bc6f0af2fbc90ac293e645ce0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fe89b2f05b854847784f91127319172945c1fadd || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7178e2a8027423b2af17ab95df73a749a5b72e5b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <858d2a4f67ff69e645a43487ef7ea7f28f06deae | aef4a9ae95d1bc4f7897065011e6261026719aeb, dad1fe7db6c6519138430ac8f5e589c18f83bfc9, a7e761ba55efaa9c49e0afdd304bb78167af3429, cd644e6dc72eec8d9d988717ea1c54f8668ded69, 9ed654e340f4c73bc6f0af2fbc90ac293e645ce0, fe89b2f05b854847784f91127319172945c1fadd, 7178e2a8027423b2af17ab95df73a749a5b72e5b, 858d2a4f67ff69e645a43487ef7ea7f28f06deae |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 2, 2026
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.
Quoted source text, attributed separately from HOL analysis.