CVE-2026-98524

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

GHSA-wq82-wxrv-wcj7 ↗EUVD-2026-103569 ↗

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.6
fixed in 1be3211e6ac77adbb1eac01314d989d243b32c59, c42d316163f89cd23de2f3e24558177a8c29bad8, 8dca3c81344532a7f05edb3d12f31f3009410a90, 49ba5ed0129906e0362c2e4b5e21c89b2a41e115, 4468df5bcdef959fd96494e9968f323561a45f4c, e2ee0616260080376123997488b5cf8a3870b8d9, b36d32f30c3f1e58e3a5ae79d0f52836a316b36e, 58eb1b3325edac42dc6df72c80962bd53a3c8ca7
ETK-2026-2213Zero's internal tracking ID, independent of the CVE number., permanent identifier
9h 05msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+52h47m
0
+2h
+4h
+6h
+8h
+10h

description

The Linux kernel RDS over InfiniBand component can retain a stale scatterlist pointer after a memory-region mapping failure. A local attacker may be able to trigger later use of the freed memory and escalate privileges; exploitation depends on reaching the affected RDS/InfiniBand memory-region handling path.

mitigation

Update to a kernel build containing one of the listed fixed revisions, including 1be3211e6ac77adbb1eac01314d989d243b32c59. Until updated, reduce exposure by disabling or restricting access to RDS over InfiniBand where it is not required.

fixed in 1be3211e6ac77adbb1eac01314d989d243b32c59, c42d316163f89cd23de2f3e24558177a8c29bad8, 8dca3c81344532a7f05edb3d12f31f3009410a90, 49ba5ed0129906e0362c2e4b5e21c89b2a41e115, 4468df5bcdef959fd96494e9968f323561a45f4c, e2ee0616260080376123997488b5cf8a3870b8d9, b36d32f30c3f1e58e3a5ae79d0f52836a316b36e, 58eb1b3325edac42dc6df72c80962bd53a3c8ca7

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.
0.22%11th percentile
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-18 15:17Z
Δ 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:17Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2213",
  "cve_id": "CVE-2026-98524",
  "display_id": "CVE-2026-98524",
  "ghsa_id": "GHSA-wq82-wxrv-wcj7",
  "euvd_id": "EUVD-2026-103569",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Use-after-free in Linux kernel RDS over InfiniBand",
  "summary": "The Linux kernel RDS over InfiniBand component can retain a stale scatterlist pointer after a memory-region mapping failure. A local attacker may be able to trigger later use of the freed memory and escalate privileges; exploitation depends on reaching the affected RDS/InfiniBand memory-region handling path.",
  "mitigation": "Update to a kernel build containing one of the listed fixed revisions, including 1be3211e6ac77adbb1eac01314d989d243b32c59. Until updated, reduce exposure by disabling or restricting access to RDS over InfiniBand where it is not required.",
  "vendor": "Linux",
  "product": "Linux",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < 1be3211e6ac77adbb1eac01314d989d243b32c59",
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < c42d316163f89cd23de2f3e24558177a8c29bad8",
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < 8dca3c81344532a7f05edb3d12f31f3009410a90",
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < 49ba5ed0129906e0362c2e4b5e21c89b2a41e115",
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < 4468df5bcdef959fd96494e9968f323561a45f4c",
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < e2ee0616260080376123997488b5cf8a3870b8d9",
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < b36d32f30c3f1e58e3a5ae79d0f52836a316b36e",
        ">= 1659185fb4d0025835eb2058a141f0746c5cab00, < 58eb1b3325edac42dc6df72c80962bd53a3c8ca7"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1be3211e6ac77adbb1eac01314d989d243b32c59",
        "c42d316163f89cd23de2f3e24558177a8c29bad8",
        "8dca3c81344532a7f05edb3d12f31f3009410a90",
        "49ba5ed0129906e0362c2e4b5e21c89b2a41e115",
        "4468df5bcdef959fd96494e9968f323561a45f4c",
        "e2ee0616260080376123997488b5cf8a3870b8d9",
        "b36d32f30c3f1e58e3a5ae79d0f52836a316b36e",
        "58eb1b3325edac42dc6df72c80962bd53a3c8ca7"
      ],
      "package_name": "Linux",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "4.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Linux",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": 0.0022,
  "epss_percentile": 0.1173,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.440314183333333,
  "t0_at": "2026-10-18T15:17:41.420000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T15:17:41.420000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-18T15:17:41.420000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-98524"
    }
  }
}

published 2026-10-20 19:56Z
last change 2026-10-21 03:59Z

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.