{
  "acceptance_criteria": [
    "Affected product or dependency presence is confirmed by a human.",
    "Affected version is confirmed or marked not applicable.",
    "Official advisory or source reference is reviewed.",
    "Patch, fixed version, mitigation, workaround, or monitor-only decision is documented.",
    "Validation steps are proposed without external scanning or production mutation."
  ],
  "affected_context": {
    "component": null,
    "cpe": [],
    "ecosystems": [],
    "product": "Kernel",
    "purl": [],
    "vendor": null,
    "versions": []
  },
  "canonical_signal_url": "https://vuln.signal-radar.com/vuln/public-candidate/CVE-2026-64269/",
  "cve_id": "CVE-2026-64269",
  "generated_at": "2026-08-01T06:18:01.437367+00:00",
  "human_checklist": [
    "Confirm whether the listed product or package is present.",
    "Confirm affected version.",
    "Review vendor advisory or official source.",
    "Confirm patch, fixed version, mitigation, workaround, or monitor-only decision.",
    "Confirm exposure.",
    "Document remediation status."
  ],
  "pack_version": "remediation-handoff/0.1",
  "redaction_policy": {
    "exploit_steps_removed": true,
    "payloads_removed": true,
    "scanner_instructions_removed": true,
    "source_published_defensive_context_allowed": true
  },
  "remediation_context": {
    "fixed_versions": [],
    "mitigation_notes": [
      "Remediation reference present; patch status requires confirmation in the linked advisory.",
      "Patch status requires confirmation from the linked advisory or official source."
    ],
    "patch_status": "requires_confirmation",
    "recommended_route": "vendor_patch_or_mitigation",
    "reference_status": "official_reference_present"
  },
  "risk_context": {
    "cvss_label": "CRITICAL",
    "cvss_score": 9.1,
    "epss_percentile": 0.48786,
    "kev_status": "not_listed",
    "risk_flags": [
      "CVSS CRITICAL",
      "official reference present"
    ],
    "severity": "CRITICAL"
  },
  "rollback_note": "If remediation work is later performed, define a project-specific rollback plan before changing any production system.",
  "safe_agent_handoff": {
    "allowed_actions": [
      "summarize vendor guidance",
      "prepare a defensive remediation plan",
      "identify affected dependencies only when repo context is separately provided by the user",
      "suggest tests and validation steps",
      "document human verification questions"
    ],
    "auto_remediation_allowed": false,
    "disallowed_actions": [
      "generate offensive code",
      "provide payloads",
      "scan external targets",
      "change production systems",
      "merge or deploy changes",
      "create GitHub issues or pull requests without explicit separate approval"
    ],
    "external_execution_allowed": false,
    "goal": "Prepare a defensive remediation plan for CVE-2026-64269 using only provided public-safe source context and any separate repo context supplied by the user.",
    "human_approval_required": true,
    "scan_allowed": false
  },
  "safety_notes": [
    "Defensive triage and remediation planning only.",
    "No offensive procedure, payload material, external target scan, or auto-remediation instruction is included.",
    "KEV not listed means not listed in the KEV catalog for this record; it does not prove absence of exploitation."
  ],
  "source_context": {
    "references": [
      "https://nvd.nist.gov/vuln/detail/CVE-2026-64269",
      "https://osv.dev/vulnerability/CVE-2026-64269"
    ],
    "source_names": [
      "NVD",
      "OSV",
      "Vendor Advisory"
    ],
    "source_published_impact": "This critical severity issue needs human triage to confirm exposure, affected versions, and vendor guidance for critical severity review.",
    "source_published_summary": "NVD: In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE... NVD: Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read())... NVD: The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the"
  }
}