CVE-2026-98432

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qp6h-4hvh-qqqc ↗EUVD-2026-102025 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Linux 4.4
fixed in b3b027ef0cd322bfa839b9aaf5b27551eea54cf6, 95a8c8fa9f27dce64c40c41c062de7728bf34ab5, 89b5b1eb7d633c33832b7ff2c02e19a144705036, 742f73df544e03744f2981c467d6542fe8172a2a, 11a03ce3c4a62d84c10ccdfe47f8075006498568, a47406c769f72c070386985488f1c4d057df86b2, 26d4c36d318cffbbd160884a0e4cec0da4da4936, e3f33b0a1d89d738e2b913dab519226eaf76e15b
ETK-2026-3117Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 00msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+369h37m
0
+2h
+4h
+6h
+8h
+10h

description

Affected Linux kernels can release IPv4 TCP option data while concurrent request processing still uses it. An attacker able to reach an IPv4 TCP service and induce relevant concurrent connection or retransmission handling may trigger a use-after-free; TCP request migration adds another affected path when enabled.

mitigation

Install your distribution's kernel update that includes the upstream fix. Until then, disable TCP request migration by setting net.ipv4.tcp_migrate_req=0 where feasible; this reduces only the migration-related exposure.

fixed in b3b027ef0cd322bfa839b9aaf5b27551eea54cf6, 95a8c8fa9f27dce64c40c41c062de7728bf34ab5, 89b5b1eb7d633c33832b7ff2c02e19a144705036, 742f73df544e03744f2981c467d6542fe8172a2a, 11a03ce3c4a62d84c10ccdfe47f8075006498568, a47406c769f72c070386985488f1c4d057df86b2, 26d4c36d318cffbbd160884a0e4cec0da4da4936, e3f33b0a1d89d738e2b913dab519226eaf76e15b

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 12:08Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-15 12:08Z
  2. 2026-10-15 12:08Z

this entry in the feed

GET /api/v1/feed/CVE-2026-98432

{
  "etk_id": "ETK-2026-3117",
  "cve_id": "CVE-2026-98432",
  "display_id": "CVE-2026-98432",
  "ghsa_id": "GHSA-qp6h-4hvh-qqqc",
  "euvd_id": "EUVD-2026-102025",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Use-after-free in Linux IPv4 TCP option handling",
  "summary": "Affected Linux kernels can release IPv4 TCP option data while concurrent request processing still uses it. An attacker able to reach an IPv4 TCP service and induce relevant concurrent connection or retransmission handling may trigger a use-after-free; TCP request migration adds another affected path when enabled.",
  "mitigation": "Install your distribution's kernel update that includes the upstream fix. Until then, disable TCP request migration by setting net.ipv4.tcp_migrate_req=0 where feasible; this reduces only the migration-related exposure.",
  "vendor": "Linux",
  "product": "Linux",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < b3b027ef0cd322bfa839b9aaf5b27551eea54cf6",
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < 95a8c8fa9f27dce64c40c41c062de7728bf34ab5",
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < 89b5b1eb7d633c33832b7ff2c02e19a144705036",
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < 742f73df544e03744f2981c467d6542fe8172a2a",
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < 11a03ce3c4a62d84c10ccdfe47f8075006498568",
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < a47406c769f72c070386985488f1c4d057df86b2",
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < 26d4c36d318cffbbd160884a0e4cec0da4da4936",
        ">= 079096f103faca2dd87342cca6f23d4b34da8871, < e3f33b0a1d89d738e2b913dab519226eaf76e15b"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "b3b027ef0cd322bfa839b9aaf5b27551eea54cf6",
        "95a8c8fa9f27dce64c40c41c062de7728bf34ab5",
        "89b5b1eb7d633c33832b7ff2c02e19a144705036",
        "742f73df544e03744f2981c467d6542fe8172a2a",
        "11a03ce3c4a62d84c10ccdfe47f8075006498568",
        "a47406c769f72c070386985488f1c4d057df86b2",
        "26d4c36d318cffbbd160884a0e4cec0da4da4936",
        "e3f33b0a1d89d738e2b913dab519226eaf76e15b"
      ],
      "package_name": "Linux",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "4.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Linux",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.0858071,
  "t0_at": "2026-10-15T12:08:22.205000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T12:08:22.205000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T12:08:22.205000+00:00",
      "url": "https://www.bleepingcomputer.com/news/security/linux-kernel-exploit-enables-remote-root-attacks-on-mptcp-servers/"
    }
  }
}

published 2026-10-30 21:35Z
last change 2026-10-31 01:48Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.