CVE-2026-98805

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

GHSA-c3cw-v3mg-q5gm ↗EUVD-2026-103890 ↗

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 5.5
fixed in 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2, f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0, 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c, 512ccd3d0e91e791fb37442aa0a2599aca19783d
ETK-2026-2508Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 26msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+101h50m
0
+2h
+4h
+6h
+8h
+10h

description

Linux kernels using TIPC encrypted communication can reuse an AES-GCM nonce after a peer changes its receiving key. An attacker able to influence the relevant TIPC peer state and capture traffic may be able to disclose protected data or produce modified traffic that is accepted as authentic.

mitigation

Install a kernel build containing the applicable fix: 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2, f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0, 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c, or 512ccd3d0e91e791fb37442aa0a2599aca19783d. Until patched, disable TIPC where it is unnecessary and limit TIPC connectivity to trusted nodes.

fixed in 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2, f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0, 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c, 512ccd3d0e91e791fb37442aa0a2599aca19783d

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
7m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-18 15:48Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-18 15:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2508",
  "cve_id": "CVE-2026-98805",
  "display_id": "CVE-2026-98805",
  "ghsa_id": "GHSA-c3cw-v3mg-q5gm",
  "euvd_id": "EUVD-2026-103890",
  "status": "published",
  "anchor_state": "anchored",
  "title": "GCM nonce reuse in Linux kernel TIPC encryption",
  "summary": "Linux kernels using TIPC encrypted communication can reuse an AES-GCM nonce after a peer changes its receiving key. An attacker able to influence the relevant TIPC peer state and capture traffic may be able to disclose protected data or produce modified traffic that is accepted as authentic.",
  "mitigation": "Install a kernel build containing the applicable fix: 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2, f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0, 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c, or 512ccd3d0e91e791fb37442aa0a2599aca19783d. Until patched, disable TIPC where it is unnecessary and limit TIPC connectivity to trusted nodes.",
  "vendor": "Linux",
  "product": "Linux",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2",
        ">= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0",
        ">= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c",
        ">= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0, < 512ccd3d0e91e791fb37442aa0a2599aca19783d"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5c8ce13c792e28d56f9ec3cd6728d8225bc0e3a2",
        "f74f100e49588c1dbdc6ab3ba9e2c67b36d015d0",
        "60e0c2aeaa605ff19ca4e65126a35643d4d7ee1c",
        "512ccd3d0e91e791fb37442aa0a2599aca19783d"
      ],
      "package_name": "Linux",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "5.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Linux",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 7.29671225,
  "t0_at": "2026-10-18T15:48:51.902000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T15:48:51.902000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-18T15:48:51.902000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-98805"
    }
  }
}

published 2026-10-22 21:31Z
last change 2026-10-22 22:51Z

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.