Skip to content

OBS-2025-000174: CVE-2025-39964

1. Observe What changed? →
2. Understand Why does it matter? →
3. Track How does risk evolve? →
4. Predict What happens next? →
5. Decide What to do? →
6. Verify What happened? →
7. Remember Persistent memory
IMMUTABLE CANONICAL OBSERVATION

OBS-2025-000174

Target Entity: CVE-2025-39964 — Linux Kernel Crypto AF_ALG Concurrent Write Race Condition

MODE: RETROSPECTIVE

Methodology: HTS-3.1
Observed UTC:
2025-09-02T00:00:00.000Z
Event Date:
2025-09-02
Epistemic State:
● KNOWN
Cryptographic Digest:
sha256-1f91766a55e7045…

This canonical observation confirms the following factual event on the threat surface:

Hermes Threat Score (HTS)
62 / 100
MEDIUM
CVSS v3.1
N/A
Not Available
EPSS (30-Day Exploitation)
N/A
Percentile: N/A
Weaponization & CISA KEV

🛡️ Not in KEV

Exploit Maturity: poc

Hermes rejects false certainty and explicitly exposes its decomposed confidence vector:

Evidence Integrity98%
Model Stability96%
Data Completeness95%
Actionable Decisiveness95%

Observation OBS-2025-000174 is strictly anchored to verified records from the following primary entities:

  • CISA KEV
  • NVD
  • Hermes Codex Research

Primary Source → OBS-2025-000174 → CVE-2025-39964 → Risk Trajectory → Action Directive


4. Target Entity & Correlated Intelligence

Section titled “4. Target Entity & Correlated Intelligence”

5. Observation Sequence & Chain of Custody

Section titled “5. Observation Sequence & Chain of Custody”

Chronological lineage for entity CVE-2025-39964:

Observation IDDateModeScoreObserved Fact
OBS-2025-0001732025-08-10RETROSPECTIVE48Initial upstream commit submitted to kernel crypto subsystem.
👉 OBS-2025-0001742025-09-02RETROSPECTIVE62Public advisory published; theoretical local DoS rated CVSS 5.5.
OBS-2026-0001752026-09-18LIVE88CISA adds to KEV catalog citing active exploitation in the wild.
OBS-2026-0001762026-09-19LIVE91Public functional LPE exploit repository published by n1k0oowang.

6. Reproducibility & Cryptographic Verification

Section titled “6. Reproducibility & Cryptographic Verification”

(Section 77 Mandate: “Observations must be reproducible”)

Fetch and verify this observation record directly from the machine-readable API:

Terminal window
# 1. Fetch canonical observation record
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2025-000174.json
# 2. Verify cryptographic SHA-256 integrity
curl -sSL https://hermes-codex.vercel.app/api/observations/OBS-2025-000174.json | sha256sum
{
"type": "observed-data",
"spec_version": "2.1",
"id": "observed-data--d5cb9a9a-da6a-a692-f283-8cb304aedeab",
"created_by_ref": "identity--hermes-codex-threat-observatory",
"created": "2025-09-02T00:00:00.000Z",
"modified": "2025-09-02T00:00:00.000Z",
"first_observed": "2025-09-02T00:00:00.000Z",
"last_observed": "2025-09-02T00:00:00.000Z",
"number_observed": 1,
"external_references": [
{
"source_name": "hermes-codex",
"external_id": "OBS-2025-000174",
"url": "https://hermes-codex.vercel.app/observations/obs-2025-000174/"
}
],
"object_marking_refs": [
"marking-definition--tlp-clear"
],
"custom_properties": {
"x_hermes_threat_score": 62,
"x_hermes_severity": "MEDIUM",
"x_hermes_epistemic_state": "KNOWN",
"x_hermes_methodology": "HTS-3.1",
"x_hermes_integrity_hash": "sha256-1f91766a55e704554611054a9f2100cca639875c71cde7baf7b8324a4e37d81b"
}
}