CVE-2026-43198

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-06. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (13)

Auto-updated Aug 19, 2026
No patch confirmed yet.
generic

tcp: fix potential race in tcp_v6_syn_recv_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/858d2a4f67ff69e645a43487ef7ea7f28f06deae
generic

tcp: fix potential race in tcp_v6_syn_recv_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7178e2a8027423b2af17ab95df73a749a5b72e5b
generic

tcp: fix potential race in tcp_v6_syn_recv_sock() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe89b2f05b854847784f91127319172945c1fadd
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support and Red Hat Enterprise Linux 8.6 Extended Update Support

https://access.redhat.com/errata/RHSA-2026:35894
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions and Red Hat Enterprise Linux 8.8 Telecommunications Update Serv

https://access.redhat.com/errata/RHSA-2026:35863
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions.

https://access.redhat.com/errata/RHSA-2026:34443
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.6 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:34094
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33285
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:33215
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:30129
redhat Patch Available

2467228 – (CVE-2026-43198) CVE-2026-43198 kernel: tcp: fix potential race in tcp_v6_syn_recv_sock()

Affected: Red Hat Enterprise Linux 10

https://bugzilla.redhat.com/show_bug.cgi?id=2467228
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-43198

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:3.10.0-1160.155.1.rt56.1307.el72026-07-17redhat
redhatkernel-0:3.10.0-1160.155.1.el72026-07-07redhat
redhatkernel-0:5.14.0-284.179.1.el9_22026-07-07redhat
redhatkernel-0:4.18.0-553.140.1.el8_102026-07-07redhat
redhatkernel-rt-0:4.18.0-553.140.1.rt7.481.el8_102026-07-07redhat
redhatkernel-0:4.18.0-372.199.1.el8_62026-07-06redhat
redhatkernel-0:4.18.0-305.197.1.el8_42026-07-06redhat
redhatkernel-0:4.18.0-477.150.1.el8_82026-07-06redhat
redhatkernel-rt-0:5.14.0-284.179.1.rt14.464.el9_22026-07-06redhat
redhatkernel-0:5.14.0-427.135.1.el9_42026-07-01redhat
redhatkernel-0:5.14.0-570.125.1.el9_62026-07-01redhat
redhatkernel-0:5.14.0-687.20.1.el9_82026-06-30redhat
redhatkernel-0:6.12.0-55.84.1.el10_02026-06-29redhat
redhatkernel-0:6.12.0-211.28.1.el10_22026-06-25redhat
linuxKernel @ 6.18.16osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 23× in last 7d / 149× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 306 total refreshes for this CVE.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 12:56 UTCEG score recompute
  6. 2026-08-17 12:56 UTCVendor advisory
  7. 2026-08-17 12:56 UTCGHSA enrichment
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 09:13 UTCVendor advisory
  10. 2026-08-16 09:13 UTCGHSA enrichment
  11. 2026-08-16 04:53 UTCEG score recompute
  12. 2026-08-16 04:53 UTCVendor advisory
  13. 2026-08-16 04:53 UTCGHSA enrichment
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-15 01:01 UTCVendor advisory
  17. 2026-08-15 01:01 UTCGHSA enrichment
  18. 2026-08-14 20:42 UTCVendor advisory
  19. 2026-08-14 20:42 UTCGHSA enrichment
  20. 2026-08-14 16:24 UTCVendor advisory
  21. 2026-08-14 16:24 UTCGHSA enrichment
  22. 2026-08-14 12:05 UTCVendor advisory
  23. 2026-08-14 12:05 UTCGHSA enrichment
  24. 2026-08-14 07:46 UTCVendor advisory
  25. 2026-08-14 07:46 UTCGHSA enrichment
Show 75 more
  1. 2026-08-14 03:28 UTCEG score recompute
  2. 2026-08-14 03:28 UTCVendor advisory
  3. 2026-08-14 03:28 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 10:49 UTCVendor advisory
  6. 2026-08-13 10:49 UTCGHSA enrichment
  7. 2026-08-13 06:07 UTCVendor advisory
  8. 2026-08-13 06:07 UTCGHSA enrichment
  9. 2026-08-13 01:38 UTCVendor advisory
  10. 2026-08-13 01:38 UTCGHSA enrichment
  11. 2026-08-12 21:19 UTCVendor advisory
  12. 2026-08-12 21:19 UTCGHSA enrichment
  13. 2026-08-12 17:01 UTCEG score recompute
  14. 2026-08-12 17:01 UTCVendor advisory
  15. 2026-08-12 17:01 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-12 00:37 UTCVendor advisory
  18. 2026-08-12 00:37 UTCGHSA enrichment
  19. 2026-08-11 20:19 UTCVendor advisory
  20. 2026-08-11 20:19 UTCGHSA enrichment
  21. 2026-08-11 16:00 UTCEG score recompute
  22. 2026-08-11 16:00 UTCVendor advisory
  23. 2026-08-11 16:00 UTCGHSA enrichment
  24. 2026-08-11 13:43 UTCEPSS rescore
  25. 2026-08-11 11:00 UTCVendor advisory
  26. 2026-08-11 11:00 UTCGHSA enrichment
  27. 2026-08-11 05:50 UTCVendor advisory
  28. 2026-08-11 05:50 UTCGHSA enrichment
  29. 2026-08-11 01:32 UTCEG score recompute
  30. 2026-08-11 01:32 UTCVendor advisory
  31. 2026-08-11 01:32 UTCGHSA enrichment
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-10 10:07 UTCVendor advisory
  34. 2026-08-10 10:06 UTCGHSA enrichment
  35. 2026-08-10 05:47 UTCVendor advisory
  36. 2026-08-10 05:47 UTCGHSA enrichment
  37. 2026-08-10 01:29 UTCVendor advisory
  38. 2026-08-10 01:29 UTCGHSA enrichment
  39. 2026-08-09 21:09 UTCVendor advisory
  40. 2026-08-09 21:09 UTCGHSA enrichment
  41. 2026-08-09 16:50 UTCEG score recompute
  42. 2026-08-09 16:50 UTCVendor advisory
  43. 2026-08-09 16:50 UTCGHSA enrichment
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-09 12:32 UTCVendor advisory
  46. 2026-08-09 12:32 UTCGHSA enrichment
  47. 2026-08-09 06:54 UTCVendor advisory
  48. 2026-08-09 06:54 UTCGHSA enrichment
  49. 2026-08-09 02:35 UTCEG score recompute
  50. 2026-08-09 02:35 UTCVendor advisory
  51. 2026-08-09 02:35 UTCGHSA enrichment
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 13:07 UTCVendor advisory
  54. 2026-08-08 13:07 UTCGHSA enrichment
  55. 2026-08-08 08:47 UTCVendor advisory
  56. 2026-08-08 08:47 UTCGHSA enrichment
  57. 2026-08-08 04:28 UTCVendor advisory
  58. 2026-08-08 04:28 UTCGHSA enrichment
  59. 2026-08-08 00:10 UTCVendor advisory
  60. 2026-08-08 00:10 UTCGHSA enrichment
  61. 2026-08-07 19:51 UTCEG score recompute
  62. 2026-08-07 19:51 UTCVendor advisory
  63. 2026-08-07 19:51 UTCGHSA enrichment
  64. 2026-08-07 15:32 UTCVendor advisory
  65. 2026-08-07 15:32 UTCGHSA enrichment
  66. 2026-08-07 11:14 UTCVendor advisory
  67. 2026-08-07 11:14 UTCGHSA enrichment
  68. 2026-08-07 01:54 UTCVendor advisory
  69. 2026-08-07 01:54 UTCGHSA enrichment
  70. 2026-08-06 21:13 UTCVendor advisory
  71. 2026-08-06 21:13 UTCGHSA enrichment
  72. 2026-08-06 16:54 UTCEG score recompute
  73. 2026-08-06 16:54 UTCVendor advisory
  74. 2026-08-06 16:54 UTCGHSA enrichment
  75. 2026-08-06 13:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43198?
CVE-2026-43198 is a critical vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: tcp: fix potential race in tcpv6synrecvsock() Code in tcpv6synrecvsock() after the call to tcpv4synrecvsock() is done too late. After tcpv4synrecvsock(), the child socket is already visible from TCP ehash table and other cpus might…
When was CVE-2026-43198 disclosed?
CVE-2026-43198 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43198 actively exploited?
CVE-2026-43198 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.5% of all scored CVEs.
What is the CVSS score of CVE-2026-43198?
CVE-2026-43198 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43198?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43198, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43198

Explore →

Is Your Infrastructure Affected by CVE-2026-43198?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.